Windows 10: SSR 2013 R2 install fails, faulting application _Setup.exe

[MIXIT]

Hi all.  I have a freshly built Windows 10 Enterprise PC in front of me, so far the only thinkgs bsides the OS and its updates installed are SEP 12.1.6 MP1 and Logitech Setpoint for the mouse/keyboard. 

I try running the installation for SSR 2013 R2 on this system using the download .zip file from FileConnect, and it loads the install browser (where you can click Getting Started, or do the install routine).  I click Install Now, and the window pops up with the initial progress bar which only runs for about 2 seconds before it disappears with no errors on screen.  Re-running produces identical results, same after reboots and re-downloading the installer package.  I've also downloaded two versions of the installer page with slightly different build numbers. 

The application event log for Windows shows two direct errors to this, event ID 1026, source is .Net Runtime, and it basically indicates generically that _Setup.exe was the faulting application.  Event 1000 follows which is pasted below.  Yet I installed the same version of SSR to another Windows 10 (Pro, not Ent.) today and it ran fine.  Any idea what this could be?   

Log Name:      Application
Source:        Application Error
Date:          9/3/2015 12:07:32 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      COMPUTER
Description:
Faulting application name: _Setup.exe, version: 15.0.16.0, time stamp: 0x53639516
Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3
Exception code: 0xe0434352
Fault offset: 0x000000000002a1c8
Faulting process id: 0xfd8
Faulting application start time: 0x01d0e67bc92ebea5
Faulting application path: C:\!IT\Sym_System_Recovery_2013R2_11.1.2.54477_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 267fc8ef-b576-4b92-881d-a3d2b8e6c3ef
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-09-03T19:07:32.000000000Z" />
    <EventRecordID>507</EventRecordID>
    <Channel>Application</Channel>
    <Computer>COMPUTER</Computer>
    <Security />
  </System>
  <EventData>
    <Data>_Setup.exe</Data>
    <Data>15.0.16.0</Data>
    <Data>53639516</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.10240.16384</Data>
    <Data>559f38c3</Data>
    <Data>e0434352</Data>
    <Data>000000000002a1c8</Data>
    <Data>fd8</Data>
    <Data>01d0e67bc92ebea5</Data>
    <Data>C:\!IT\Sym_System_Recovery_2013R2_11.1.2.54477_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>267fc8ef-b576-4b92-881d-a3d2b8e6c3ef</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[lmosla · Accepted solution]

this should help http://www.symantec.com/docs/TECH215227

[MIXIT]

Thanks Imosla.  I gave it a try and that worked.  However I also learned today that SSR 2013 R2 is not supported on Windows 10 yet, most annoying :) So while I"m glad to have it installed, I won't bother trying to use it until Symantec produces SP4 (or R3, whichever it'll be called).  I know there are workarounds for the license key issue and for creation of the SRD, but frankly those were only prompted by a host of complaining usrs and weren't considered official fixes, so in my mind it's not smart to implement a DR solution based on an unsupported platform and using ad hoc workarounds.  Though I'm sure these same workarounds will end up as part of the official SP4, for now, they're unofficial so not worth the liability. 

Thanks again. 

[criley]

Though I'm sure these same workarounds will end up as part of the official SP4, for now, they're unofficial so not worth the liability.

The license fix is official now. Details here: http://www.symantec.com/docs/TECH231698.