Setup error: "Interactive sign-in process initialization has failed."

WizKid

Member
Messages
45
Reaction score
3
Whenever I use the attached preset, I get the message:

View attachment 14052

I also still get the infamous "Windows setup has failed." error message after 80% when doing trying to do an upgrade install.

Is this a bug?
 

Attachments

Last edited:
Some parts of your preset might present a few problems:
Code:
                <c>clip 'Client License Platform'</c>
                <c>microsoft.net.native.framework.2.2 'Microsoft .Net Native Framework Package 2.2'</c>
                <c>microsoft.net.native.runtime.2.2 'Microsoft .Net Native Runtime Package 2.2'</c>
                <c>microsoft.windowsappruntime.cbs.1.6 'Windows Application Runtime v1.6'</c>
                <c>microsoftwindows.client.cbs 'Windows Feature Experience Pack - Desktop'</c>
                <c>microsoftwindows.client.core 'Windows Feature Experience Pack - Core'</c>
                <c>netframework3wcf 'Windows Communication Foundation (WCF) 3'</c>
                <c>netframework4wcf 'Windows Communication Foundation (WCF) 4'</c>
                <c>netframework4wpf 'Windows Presentation Foundation'</c>
                <c>netframework4wpfcore 'Windows Presentation Foundation (Core)'</c>
                <c>powershell</c>
                <c>sens 'System Event Notification Service (SENS)'</c>
                <c>shellappruntime 'Shell App Runtime'</c>
                <c>unp 'Universal Notification Platform (UNP)'</c>
 
I keep these components compared to your preset and no errors during installation (Windows setup has failed).
Code:
<c>comlegacyole32 'COM OLE 2.x - Legacy - 32 bit'</c>
<c>microsoft.net.native.framework.2.2 'Microsoft .Net Native Framework Package 2.2'</c>
<c>microsoft.net.native.runtime.2.2 'Microsoft .Net Native Runtime Package 2.2'</c>
 
See this thread.

Same problem, different preset. Even if I keep 'microsoft.net.native.framework.2.2' it still fails with the same error.

Any help?
 

Attachments

Asking in a another thread don't help you.
But you don't remove all the cloud sh*t.
 
Last edited:
According to this preset, you didn't follow most of my previous recommendations.
 
Whenever I use the attached preset, I get the message:

I also still get the infamous "Windows setup has failed." error message after 80% when doing trying to do an upgrade install.

Is this a bug?
Hi,

confirmed, it's probably some dependency.
Will find it in order to lock for future users, regardless if it turns out to be obvious.

Thanks for reporting, will reply today.
 
Maybe one of these components (I remove all the others and no problem)

Code:
<c>devicecenter 'Device Center (Devices and Printers)'</c>
<c>devicesetupmanager 'Device Setup Manager'</c>
<c>displayswitch 'Display Switch'</c>
<c>driver_c_nvmedisk.inf</c>
<c>driver_c_wceusbs.inf</c>
 
It's not the components, it passed when I reset the Settings (most likely services) and Features (capabilities).
 
It's not the components, it passed when I reset the Settings (most likely services) and Features (capabilities).
Turns out if I disable the tweaks but keep everything else, it works... o_O

Would be nice to choose only to apply the legacy setup and TPM tweaks to boot.wim:

View attachment 14194

The fact that it applies all 61 (or however many one selects) to boot.wim sounds like a bug:

View attachment 14193

If one didn't apply all the 61 (or however many one selects) to the boot WIM it probably wouldn't bomb.
 

Attachments

Last edited:
Probably one of the disabled or manual services, like CryptSvc, NetSetupSvc or TrustedInstaller.
 
The only question is, which is it? Hopefully nuhi figures it out and locks it.
This is weird, it's the Settings - System - Boot/Setup - Legacy which is set to Default even though it's default already.
Somehow in your preset it is set like that - probably you went to Legacy and back to Default and stumbled on this bug.
Just re-set that one to Default to disable (not be bold as in pending change), and resave the preset, that should fix it.
Will fix for the next update.

Btw then you can uncheck boot.wim in Apply - Reapply - boot.wim - Settings.

Got your notion about Boot.wim selection of tweaks, it's not straightforward - but before considering technical hurdles, should not matter what is applied to boot.wim, it's actually beneficial to reflect the final deployment during setup.
Feel free to comment how you see it, with an example which setting is detrimental to boot.wim, but nice to have for install.wim?

Thanks.
 
I removed the legacy boot option and restored the services back to default and it completes fine.

I did so by deleting:

<Services>
<TweakGroup name="services">
<Tweak name="CryptSvc\CryptSvc">3</Tweak>
<Tweak name="DoSvc\DoSvc">2</Tweak>
<Tweak name="IKEEXT\IKEEXT">2</Tweak>
<Tweak name="NetSetupSvc\NetSetupSvc">3</Tweak>
<Tweak name="PcaSvc\PcaSvc">2</Tweak>
<Tweak name="Wecsvc\Wecsvc">4</Tweak>
<Tweak name="TrustedInstaller\TrustedInstaller">3</Tweak>
</TweakGroup>
</Services>

The question is what service)s) need to be locked (left unchanged) for setup to complete?
 

Attachments

Last edited:
The question is what service)s) need to be locked (left unchanged) for setup to complete?
In my test only thing was the Boot Setup/Legacy thing with Default on Default.
 
Back
Top