"Getting everything ready for you" screen taking over 9 minutes to complete

Missile

New Member
Messages
14
Reaction score
0
So I disabled the first logon animation(with regedit) and I get a preparing Windows screen that takes over 9 minutes. i tried enabling it again but it didn't fix the problem.

I also want to know how I can remove more stuff from windows to reduce install size without affecting stability(on windows 10 ltsc and free version of ntlite)

How do I fix this?
 
This doesn't look like the right preset. There's barely any changes, and none that slow down new user provisioning.

On the free edition, you're limited to a small list of Component removals which won't break Windows any way.
 
This doesn't look like the right preset. There's barely any changes, and none that slow down new user provisioning.

On the free edition, you're limited to a small list of Component removals which won't break Windows any way.
How? I modified the ISO by disabling telementry and other microsoft data sending stuff, disabling some features, removing microsoft edge and some changes in settings.

I also tried getting a fresh install.wim from a fresh ISO and after I loaded the preset the problem arrived
 
The only changes in this preset are a few tweaks. Open it up in Notepad, and see for yourself. Are there other Auto-saved files sitting around?
 
Sorry for the late reply. I've come to the conclusion that the personalization settings might be causing the issue. But even after not changing any personalization-related settings in ntlite I still have the same issue. The mtr preset is the preset with no personalization settings and the other with personalization setitngs, both of them have the same problem. I know it comes down to the preset even if there aren't many changes. I even got another install.wim and after loading the preset(both mtr and mtroptimizations) I got the same problem.

The reason I thought the personalization settings can be the problem and very likely is because it was applying those settings during the first logon part of the setup.
 

Attachments

There's nothing here to cause problems, except you're skipping the Online Account screen during OOBE.

It's not clear if you're using a BypassNRO setting from Rufus or another tool to get around the MS Account requirement. Normally most users will create an explicit Local User account in the unattended file, or use a bypass feature to finish this part of OOBE.
 
There's nothing here to cause problems, except you're skipping the Online Account screen during OOBE.

It's not clear if you're using a BypassNRO setting from Rufus or another tool to get around the MS Account requirement. Normally most users will create an explicit Local User account in the unattended file, or use a bypass feature to finish this part of OOBE.
Alright, that makes sense. The autoattend was created with NTLite. I'll try deleting the autoattend and see if that fixes it
 
Update: It didn't work. And for some reason when I use net user the getting ready setup takes only 26 seconds. This issue happened with a different ISO too. I can't find the cause of the issue, this happens even after I stopped using NTLite and I made my own batch file to modify the ISO that is using DISM. temporarily to see if that fixes it. And it didn't. I didn't find anything in windows event viewer either.
 
This problem can't be solved, until you explain how you're creating a new user account. There is nothing explicit in either preset or the unattended file that creates a Local Account, so the logical thing that would happen is OOBE forces you to a create a MS Account.

Since there's no explicit BypassNRO function in the three files, either you're doing it by hand or have another tool do the mod. I don't think someone can replicate your problem using the exact details you've provided. Are you doing more extensive mods outside of NTLite?
 
This problem can't be solved, until you explain how you're creating a new user account. There is nothing explicit in either preset or the unattended file that creates a Local Account, so the logical thing that would happen is OOBE forces you to a create a MS Account.

Since there's no explicit BypassNRO function in the three files, either you're doing it by hand or have another tool do the mod. I don't think someone can replicate your problem using the exact details you've provided. Are you doing more extensive mods outside of NTLite?
No. All I used is NTlite. The user account is created via OOBE(local account)

I used DISM on a fresh ISO too and it has the same problem.
I stopped using a preset entirely and just modified a few thing:

c:\windows\web folder(taking ownership of it and replacing and adding wallpaper files)
OOBERUN.EXE, importantmsg.exe, sysrestrict.exe in windows folder (some setup files required for my mod)
logonlauncher.exe in c:\windows\system32, as well as compactmgr.exe, autoclean.exe, and mtrlogo.exe. Again, some mod executables.

And 2 registry changes:

LabConfig with Bypassa CPU and RAM requirements (my laptop which i test this on meets the system requirements and with a regular iso it completes in 26 seconds. When I create another user after the main user is created after the OOBE it takes less than 30 seconds. This problem is only specific to creating the first user)

logonlauncher string in HKLM\SOFTWARE\Microsoft\Windows\Currentversion\runonce with this data inside:

C:\Windows\System32\logonlauncher.exe

I'm trying to bypass the microsoft account in the OOBE using the unattend tab in NTLite. But removing the autoattend.xml file didn't help at all and it's the same as keeping it
 
To bypass MS Account setup all you need is NTLite's BypassNRO setting (licensed edition) or to integrate the same reg key into install.wim (free edition). I have no idea what you're doing with the other OOBE files, and all that is probably unsupported in normal Windows.

OOBE doesn't just "answer a few questions", it also does UWP app provisioning in the background.
 
To bypass MS Account setup all you need is NTLite's BypassNRO setting (licensed edition) or to integrate the same reg key into install.wim (free edition). I have no idea what you're doing with the other OOBE files, and all that is probably unsupported in normal Windows.

OOBE doesn't just "answer a few questions", it also does UWP app provisioning in the background.
I'm not modifying any OOBE files. And those files are just for my additional stuff. I'm trying to make a windows mod with custom features.
 
Back
Top