No Boot: Windows 10 2004 19041.21 - Dism /resetbase

FLCL

New Member
Hi Guys :),

it's just a test but maybe ist helpful for someone especially Nuhi.

If the KB4535550 is installed and I want to cleanup with dism -resetbase (enabled via NTlite) the next restart will be the last.
Bootin' stops at the turning circles.

Does anybody get the same problem?


Greetings FLCL
 

Attachments

nuhi

NTLite developer
Staff member
Thanks, but Win10 2004 19041.21 is not supported at this moment, can't even boot the latest build (.21) intact on VMWare.

Give them some time, will make sure to add this test and reply here when I get a working intact ISO.
 

FLCL

New Member
@ nuhi
I know that. Like I said just a test which could be helpful for ya :).
As far as I know form my digital life forum a clean install with .21 will definitifly not work.

@ cosmasebastian
Thank you!
 

mentro

Member
If you take the boot.wim from the 19041.1 iso and put it in the 19041.21 iso it will boot fine and I also used it with ntlite and no problems so far. I.m using pro en-us x64 .
 

nuhi

NTLite developer
Staff member
If you take the boot.wim from the 19041.1 iso and put it in the 19041.21 iso it will boot fine and I also used it with ntlite and no problems so far. I.m using pro en-us x64 .
This puts me to shame, too obvious! :) Appreciated.
 

nuhi

NTLite developer
Staff member
FLCL, ook, had to abort this, seems like it's a Windows bug/feature.
Out of curiosity tested the full OS + ResetBase tweak only + DISM CleanUpdates ResetBase, and it had the same boot loop issue on reboot.

So, will be removing either the tweak or the cleanup option for the 2004, depending on the size comparisons and what makes more sense while retaining the booting of course.
Also will need to revisit this with the newer 2004 builds, in case it gets fixed by them.

Thanks anyway, interesting find.
 

FLCL

New Member
With kb4539080 the problem seems to be solved.
Testing right now.

Edit: It's working :)
 
Last edited:

nuhi

NTLite developer
Staff member
Oo great, I was just about to test this.
Thanks for the info.

Note to self: it's not always MS's fault, now don't delete all reports
 
Top