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

KB5001330 - having issues with netbios working after this patch is installed, I have had to remove this on about 6 machines so far to get network traffic working again.

@chrisbarton462, 

I just use the default settings. My local network traffic seems fine.

What kind of problems do you see? 

Did you file an FBH report ? 

Not knowing when the 21H1 MCT will be available, I just made this for now. :-)

Hi fg,

How did you make this ISO. Have you tried to use it? Does it install?

I have had no luck so far. Always an issue converting the wim to esd in wimlib56/57. I then tried letting dump make this ISO which it did (it still uses v56, not v57). Copied it to bootable flash, it would not do an in-place upgrade on laptop, reported error 0x8007025D - 0x2000C (Installation cancelled in Safe OS phase). 

This normally means corrupt installation file or bad USB drive. Proceeded to try a total clean install from same ISO image to vm, same error. Deleted.

Then tried creating the ISO using install.wim, it did install ok in vm, so took the install.wim and tried to convert it to install.esd. Nope, ESD2WIM reports error in wim file.

Ended up doing the in-place on laptop using the RP image, successfully converted that install.wim to install.esd for flash card. Yep, I could of used the image and mounted but wanted to check the flash card.

Regards,

Not knowing when the 21H1 MCT will be available, I just made this for now. :-)

Hi fg,

How did you make this ISO. Have you tried to use it? Does it install?

I have had no luck so far. Always an issue converting the wim to esd in wimlib56/57. I then tried letting dump make this ISO which it did (it still uses v56, not v57). Copied it to bootable flash, it would not do an in-place upgrade on laptop, reported error 0x8007025D - 0x2000C (Installation cancelled in Safe OS phase). 

This normally means corrupt installation file or bad USB drive. Proceeded to try a total clean install from same ISO image to vm, same error. Deleted.

Then tried creating the ISO using install.wim, it did install ok in vm, so took the install.wim and tried to convert it to install.esd. Nope, ESD2WIM reports error in wim file.

Ended up doing the in-place on laptop using the RP image, successfully converted that install.wim to install.esd for flash card. Yep, I could of used the image and mounted but wanted to check the flash card.

Regards,

Hi Johnny, 

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.

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,

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.