"Just a moment" Loop

D

dkdubya2

Member
Messages
32
Reaction score
7
I had to come back to doing new NTLite sessions with my copy of Windows 10 build 1903, after the motherboard had to be replaced on my custom PC with a different brand which require different drivers so I couldn't use the very last saved installation ISO I burned to USB for the fresh install (also had to update some post-setup apps); sadly the USB with the last saved installation stopped working.

But I have experienced a "Just A Moment" loop at the near-end of installation with each, completed new session ISO tested in Virtualbox, even using 2 extracted previous working slipstreamed ISOs (but not completely tweaked to my satisfaction) I had managed to save for sources; this loop also took place with the first new session I did before I updated NTLite to the latest version.

Just curious if anyone else is dealing with this particular issue I now can't seem to get past, I've made no unusual tweaks that would alter the extracted Win. 10 structure during the sessions, in fact, I used a saved session file from one of the saved, working ISOs for one session to see if that would resolve the issue, but to no avail, any advice to help me get rid of this loop would be appreciated, thanks.


View attachment 6249
 
Last edited:
clrkz said:
kindly check pls ty
Click to expand...
You don't delete any drivers, but just in case, what PC are you using ?
Maybe you need the Intel RST driver

I see AMD and Intel in the drivers, and besides some drivers are duplicated (HECI, iclsclient, etc...) any particular reason ?
 
Im using gigabyte z790 aorus elite x wifi 7 i9 14900kf, sorry but in not that well in computers, i have intel driver like z700 inf chipset, what particular driver do i need? I think i got intel bootdisk rist, HSACOMPONENT, HSAEXTENSION, VMD.
 
At this point, it's probably not a missing driver
The problem is elsewhere

Just a moment... that's at what "moment" of the installation it appears (can't remember) ?
I don't have all that with the autounattend.xml
 
Ok, if it remains stuck on this "window" it would probably come from a deleted component
Or it's just long, but the installation finishes?
 
not finishing, just keep entering a page when restarted, why you got restarted, and keeping on that loop for more than 5 hours then i go force reformat with clean.
 
It looks like you disable stuff related to both wired and wireless connections in components and services. The integrated drivers seem suspect too. I'd try an image that enables a network and eliminates all integrated drivers, then see what happens. Also, have you tried a default W11 24H2 installation to compare?
 
Last edited:
I have been making test ISOs for an educational facility for the better part of a year. Used Hellbovine's guide as a base and made adjustments as necessary. Just a few days ago I was able to make an updated ISO and get it installed. Made a few changes to Post-Setup and cleaned up the XML preset files since I usually work in sections.

I honestly don't know where it all went wrong, but now Windows installs, reboots and get stuck on the "Just a moment" page. I must have remade the ISO several times already and I cannot figure out why Windows is getting stuck. Last time this happened it was something with the Unattended file, but I haven't changed that file in several months. I even tried remaking it, nothing changed. If I force the PC to shutdown and turn it on again, it gets stuck on the Post-Setup command prompt while mentioning that the WIFI service is not working.

For added context, I always start with an untouched MS ISO, update it, process it, then do component removals, process it, and finally make any changes or add programs before a final processing.
 

Attachments

Last edited:
I think the reality is that it's simply W11 and newer builds as the main problem overall right now. It's a buggy and frustrating mess so far, as the number of threads for help has skyrocketed recently and most of them are using W11 or 24H2. There will be Microsoft bugs as well as things NTLite has to change in the tool before this settles down. W10 is much easier to work with and the licenses are interchangeable.

I mentioned that this would happen back when 23H2 was coming out, because Microsoft was making it known that future updates, especially the ones focused on implementing AI, would start to add a lot more automation and suggestions into Windows, which should be interpreted by NTLite users as more stuff that actively fights against your tweaking. People should speak with their wallets and stop using W11, because Microsoft has made it clear that their bugs, the level of lockdowns, and undoing of our tweaks will continue to get much worse in the future.

The reason Windows XP lasted so long is because people spoke up and forced Microsoft's hand. Microsoft has pushed W11 really hard by doing things like stopping sales for W10 early, deleting downloads for older operating systems, and other related sales tactics, because most people continue to use W10, since they can't stand that with every new operating system we lose overall productivity as the OS becomes more difficult and time consuming to tweak or just use on the daily. The leap between Windows XP and Windows 10 is the difference between spending 20 hours versus 1,000 hours to fully optimize, and W11 is showing that this trend has no sign of slowing, meaning W12 will be a trainwreck at this rate.

Windows has reached a milestone where it's so unnecessarily convoluted and bloated, that only the most dedicated and knowledgeable troubleshooters can fully tweak it, and that tiny group of people diminishes with each major update, such as 23H2 and beyond. This forum had a similar conversation some years ago when W11 was brand new, because people were finding that so many component removals were causing problems, that a lot of NTLite veterans just stopped using removals entirely and went to registry keys, and now that is intentionally being interfered with by Microsoft too.
 
Last edited:
Hellbovine said:
I think the reality is that it's simply W11 and newer builds as the main problem overall right now. It's a buggy and frustrating mess so far, as the number of threads for help has skyrocketed recently and most of them are using W11 or 24H2. There will be Microsoft bugs as well as things NTLite has to change in the tool before this settles down. W10 is much easier to work with and the licenses are interchangeable.....
Click to expand...
Agreed. Microsoft's constant interfering is making IT life interesting to say the least. I am not a fan of 23H2 and beyond, but it is what it is. Never has Windows been so buggy in my experience.

That said, I am fairly certain that my looping error was on my end this time, but I haven't a clue what did it.

Edit: Think I narrowed it down to the Post-Setup as expected. Changed one command and now installation completes, but the Post-Setup dialogue and command prompt show upon logging onto a profile and just stay there unless closed. Not sure what's causing that now.
 
Last edited:
You must log in or register to reply here.
Back
Top