Build 19043.928 out to Beta & Release Channel + ISO for 19043.928

Hi Johnny, 

You may be interested on this other subject.

Have you noticed the they changed the behavior of chkdsk C: /f    or   /r.

It still deletes all the Feature Configurations that are added in group 4 including the configuration for N&I, but even with the configurations deleted, N&I maintains the previous status, in other words if it was enabled you will still get it even if the configuration disappears, if it was disabled it will stay disabled.

It looks like they save the configuration in some other place or they changed the default to leave it enabled even if the configuration is missing.

Why they clear up the feature configurations on chkdsk is still a mystery to me and there is no answer from MS ?

vivetool addconfig 27371152  2 1 6 0 0 4   (N&I Default Enabled with Hover variant)

[0x01A1A690 / 27371152]

Group: 4

EnabledState: Enabled (2)

EnabledStateOptions: 1

Variant: 6

VariantPayloadKind: 0

VariantPayload: 0

______________________________________________________________________________________________

vivetool addconfig 27371152  1 1 0 0 0 4   (N&I Disabled)

[0x01A1A690 / 27371152]

Group: 4

EnabledState: Disabled (1)

EnabledStateOptions: 1

Variant: 0

VariantPayloadKind: 0

VariantPayload: 0

Have a Dell XPS tower setup to triple boot, 2 Win 10 Pro and 1 Win 7 Pro.  This computer to compare hardware and software.

One Win 10 Pro running 21H1developed a stall problem and also failed update to 19043.928. Tried several procedures to

recover but the stall stopped the tries.  Finally, today did a warm boot using USB with an ISO for 20H2 19042.572.  It completed

successfully.  Then did the update which brought it up to 21H1 19043.928.  Now both Win 10 Pro boots are running OK

at this new release.

 

@B2wS, 

I don't know what you mean with "warm boot" ?

If you mean that you did an Update in Place using the ISO or USB installation media, then yes  that works fine to get over the update problem from 19043.899 to 19043.928.

What was the 21H1 build level when you started getting the problems ?

I think I made this from uupdump. Sometimes I convert the .wim to .esd afterwards with DISM, but in this case I think I asked to make .esd instead of .wim . 

I used it for Update in place and Clean install without any problem.

Hi fg,

This has me stumped. Tried again today using the install.wim from working image, copied it over to esd2wim, same file used previously, this time it completed to 100% with no error. Replaced install.wim back to ISO with install.esd and mounted image for total clean install in vm. Worked.

Suspect there must be a program I use that stays in memory that caused these issues. Could it possibly be Bluestacks, as I do use the emulator to play Guns of Glory. Have not run it today yet to confirm, but use it daily. Later on will play the game and try again on same install.wim and see what happens when I compress it. Spent too much time on this one.

On a bright note, I can finally copy a working .928 to bootable FAT32 flash......again.  sigh

Regards,

Hi Johnny, 

I used DISM command to convert .wim to .esd,  I have not used the esd2wim in quite sometime, I'm not sure if that makes any difference ? 

I think you had a similar issue one time before, but never followed up with what happened that time.

Let me know if you find out what caused the problem this time.

Thanks.

Have a Dell XPS tower setup to triple boot, 2 Win 10 Pro and 1 Win 7 Pro.  This computer to compare hardware and software.

One Win 10 Pro running 21H1developed a stall problem and also failed update to 19043.928. Tried several procedures to

recover but the stall stopped the tries.  Finally, today did a warm boot using USB with an ISO for 20H2 19042.572.  It completed

successfully.  Then did the update which brought it up to 21H1 19043.928.  Now both Win 10 Pro boots are running OK

at this new release.

I think I made this from uupdump. Sometimes I convert the .wim to .esd afterwards with DISM, but in this case I think I asked to make .esd instead of .wim . 

I used it for Update in place and Clean install without any problem.

Hi fg,

This has me stumped. Tried again today using the install.wim from working image, copied it over to esd2wim, same file used previously, this time it completed to 100% with no error. Replaced install.wim back to ISO with install.esd and mounted image for total clean install in vm. Worked.

Suspect there must be a program I use that stays in memory that caused these issues. Could it possibly be Bluestacks, as I do use the emulator to play Guns of Glory. Have not run it today yet to confirm, but use it daily. Later on will play the game and try again on same install.wim and see what happens when I compress it. Spent too much time on this one.

On a bright note, I can finally copy a working .928 to bootable FAT32 flash......again.  sigh

Regards,