Windows 10 22H2 Issues

[MYK-IT]

Hi,

 

We deploy Windows 10 via MDT using an updated / cleaned WIM created via WIMWITCH.

 

To date, our desktops use a 21H2-based WIM and recently all updated to 22H2 (via WUfB) successfully too. (For ref: from 10.0.19044.2006 to currently, 10.0.19045.2130). No known problems with the enablement package being deployed / OS being updated.

 

I've recently updated and made a new Windows 10 22H2-based WIM (10.0.19042.2130, using same method) to deploy for new re/builds. Initially, deployment went ok to a selection of different models of test laptops. However, after they have been left for a period of time (e.g., latest updates being applied etc.) and rebooted the problems started.

 

• Presented with a black screen instead of showing Windows sign in screen (no cursor)
  
• Attempts to do an OS recovery fails (3 power on/off actions at manufacturer screen)
  
• Initially just affected (2 different) HP laptops (thought it may be a specific HP driver / injection issue), then a Toshiba model did the same
  
• Dell Laptops were OK, however this morning - they have same problem where upon reboot stays on Dell logo and spinning icon underneath
  
• Today, the HP laptops have gone a bit further as in now get a black screen with white cursor
  

 

 

So, last night I remade a newer Windows 22H2-based WIM (10.0.19045.2251) with the intention to try again today, deploying this new WIM to some test devices, and our original 21H2 WIM to the other test devices - to see what happens!

 

I have only come across 1 article online (to date) of someone having similar experience on their computer where they used a 22H2 ISO, but I am also aware of the many updates and OOB update in recent weeks that corrected issues with OneDrive and upgrade issues with 22H2. Therefore, hoping that my latest 22H2 'may' resolve the issue(?) and perhaps my original WIM was corrupted some way??

 

Of course, could be many of variables causing this, e.g., drivers, updates, software, AV but been unable to login / access log files as yet.

 

Otherwise, back to using our 21H2 WIM and upgrade via WUfB.

 

I will update accordingly.

 

Thanks.

Edited November 15, 2022 by MYK-IT

[ITGuyNW]

I have deployed 22H2 out in a similar way to you (WIMWITCH, MDT) and to date I've not seen any issues. That's on HP Elitebook 840s, HP Probook 440 G7s, HP 255 G7 and then some desktops including HP 800 G4s. I used 10.0.19045.2130.

 

Like you say, could it have just been a corrupted WIM?

[RLR]

We had RDP connection issues when installing 22H2 via MDT. But if we upgraded to 22H2 from 21H2 via the enablement package it was fine. It's as if the GPO RDP settings are not going into affect for 22H2 new computers.

 

Another issue I currently have is the WIM file downloaded from MVLC always extracts as version 19041 which I believe is windows version 2004? I have to add the 21H2 enablement package to upgrade the wim to 19044. Anyone else image just by extracting the WIM from the ISO or does everyone build an image and deploy that?

[MYK-IT]

I have deployed 22H2 out in a similar way to you (WIMWITCH, MDT) and to date I've not seen any issues. That's on HP Elitebook 840s, HP Probook 440 G7s, HP 255 G7 and then some desktops including HP 800 G4s. I used 10.0.19045.2130.

 

Like you say, could it have just been a corrupted WIM?

 

Good to know it's working for you (especially as same base ISO and WIM creation method).

 

Hopefully it was just a WIM corruption; only other thing I can think of is that I also install the latest OneDrive Client (22.212.1009.0004, with /allusers switch to convert to per machine installation) as part of the MDT process. Perhaps with OneDrive client being a known issue with 22H2 (and since resolved with a later update) perhaps that could be a contributing factor??

 

Currently redeploying 22H2 / 22H1 images to test devices; once Autopilot enrolled and updated etc. later, I will soon find out!

 

Thanks,

[MYK-IT]

We had RDP connection issues when installing 22H2 via MDT. But if we upgraded to 22H2 from 21H2 via the enablement package it was fine. It's as if the GPO RDP settings are not going into affect for 22H2 new computers.

 

Another issue I currently have is the WIM file downloaded from MVLC always extracts as version 19041 which I believe is windows version 2004? I have to add the 21H2 enablement package to upgrade the wim to 19044. Anyone else image just by extracting the WIM from the ISO or does everyone build an image and deploy that?

 

As @ITGuyNW, we use WIMWITCH to extract the required WIM from the ISO and to apply the latest / required updates automatically.

[MYK-IT]

Just to update, that I have managed to resolve this issue.

 

Essentially the issue I was experiencing appeared to a result of variables being set from the intended TS being combined (unintentionally) with settings from other TS defined within global customsettings.ini file.

 

After a day of researching, testing, amending customsettings.ini file, and customising scripts (DeployWiz_SelectTS.vbs) not only have I now got this additional custom (AutoPilot Device) deployment method working, but our MDT 2013 is now configured in such a way that it allows for customised sequence-based deployment, utilising TaskSequenceIDs.

 

So was certainly worth the stress and effort in the end!

Edited November 18, 2022 by MYK-IT

[gaz350b]

Would love to know if you guys are seeing no UAC prompt when trying to go into other user folders. (It’s my workstation and script saves export file it it’s user area).

 

Just click in The user folder and nothing happens.

[Sadiq_to222]

I only noticed that yesterday that the 22H2 install.wim is now a .esd

 

Not sure if it was because I didn't get it from the VLSC.