No Boot: Windows 10 2004 19041.21 - Dism /resetbase

FLCL

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

  • Automatisch gespeicherte Sitzung {1F36719C-B95C-0642-1C26-DE92AD9EB4C5}.xml
    17.3 KB
  • Automatisch gespeicherte Sitzung {47B1148A-F623-40BC-90C9-ADBA5760AD38}.xml
    11.8 KB
  • Automatisch gespeicherte Sitzung {437F952D-908D-0E4E-C619-7D7E539C9BC1}.xml
    28.5 KB
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.
 
@ 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!
 
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 .
 
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.
 
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.
 
With kb4539080 the problem seems to be solved.
Testing right now.

Edit: It's working :)
 
Last edited:
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
 
With 19041.113 there are cleanup issues again but luckily it don't break Windows.

The dism /StartComponentCleanup (resetbase) command just don't completely cleanup. There are components/packets left whicht can't be approved.
 
With 19041.113 there are cleanup issues again but luckily it don't break Windows.

The dism /StartComponentCleanup (resetbase) command just don't completely cleanup. There are components/packets left whicht can't be approved.
Is it any different on full Windows of the same version?
 
On my side, with the attached preset, I do not get any error when running /Cleanup-Image /StartComponentCleanup. Maybe this can help Nuhi going through the issue.

Fil
 

Attachments

  • Auto-saved session {6A12E04A-BBAE-4F5A-9BE1-C36A87836931}.xml
    27 KB
FLCL, thanks for the info, keep me updated, especially if you see that some issue is not a Windows "feature".
 
On my side, with the attached preset, I do not get any error when running /Cleanup-Image /StartComponentCleanup. Maybe this can help Nuhi going through the issue.

Fil
HI Fil, good preset! Please check sfc /scannow and share results. Thanks...
 
Last edited:
Back
Top