[24h2 / lts 2024] Windows 11, version 24H2: What’s new for IT pros

[DrCheese]

WMIC is apparently deprecated and off by default in 24H2. One of our computer startup bat scripts uses wmic to query the installed version of a piece of software, so doesn't work. Will have to switch to using a PowerShell method of doing it instead.

 

Yes this is annoying for us as we use this to install the right driver pack during MDT install.

 

https://emeneye.wordpress.com/2013/01/14/injecting-drivers-based-on-target-computer-model/

 

It's been done in the latest 23H2 as well as we discovered this when deploying images over the summer (Just rolled back to the previous month which got it going again)

[mavhc]

Can't remember the last time I had to add drivers, they all seem to be on Windows Update now

[Olliedawg]

Can't remember the last time I had to add drivers, they all seem to be on Windows Update now

 

I let WU handle drivers too - unless it's some specific hardware that requires a specific driver

[jthompson]

Yes this is annoying for us as we use this to install the right driver pack during MDT install.

 

https://emeneye.wordpress.com/2013/01/14/injecting-drivers-based-on-target-computer-model/

 

It's been done in the latest 23H2 as well as we discovered this when deploying images over the summer (Just rolled back to the previous month which got it going again)

 

We set up a similar method with Win10 deployment in MDT, and I had thought I'd done he same with the Win11 deployment share, but your post got me thinking so I checked. Although I've got drivers in driver groups named for each model, I must have forgotten to add the "Select Driver Group" step into the task sequence, so out Win11 deployments have just been picking drivers from the whole lot each time. Not encountered any issues out of that (Dell only here). In any case, we see newly-imaged Win11 machines grabbing drivers from WU, so there's probably something to be said for just letting machines get drivers from WUfB anyway.

 

Oh, and I'm still seeing WMIC working on an up to date 23H2 machine, which will be based on a June ISO. Which month's ISO of 23H2 is your MDT using that has WMIC disabled?

Edited October 7, 2024 by jthompson

[gshaw]

The update tied up even some of the faster machines for best part of an hour the other day so have put an InTune Feature Update policy in to defer it until half-term at least. Gives time to roll it out to a few more test machines and get new Config Profiles in place.

[mullet_man]

I've tried to push this out to a few test machines via an Intune feature update and none of the devices have picked it up.

 

Set to make available as soon as possible and make available as an optional update but hasn't come through to any of the devices.

 

Got HP Mini 400, HP ProBook 440 G9 so they all meet the spec.

 

Moving to 23H2 worked via same method!

[mullet_man]

I've tried to push this out to a few test machines via an Intune feature update and none of the devices have picked it up.

 

Set to make available as soon as possible and make available as an optional update but hasn't come through to any of the devices.

 

Got HP Mini 400, HP ProBook 440 G9 so they all meet the spec.

 

Moving to 23H2 worked via same method!

Ignore this I've sorted it. Had deferral on feature update set.

[3s-gtech]

I have just pushed this out via MDT. Older ADK, didn't update that (but it was quite recent as I did some work on it to support 14th gen Intel stuff).

 

Lenovo E14 (10th gen Intel).

 

Seems to have worked fine. Nothing fancy in the task sequence, but I don't do capture and deploy - I build from the WIM afresh.

[jthompson]

My favourite way to query for software in PowerShell is the Get-Package command. It seems to get everything apart from AppX packages.

 

I've also now made use use of Get-Item to query the product version from the properties of an installed exe. The app wasn't listed under the uninstall keys in registry, and Get-Package only returned a major version, not a detailed enough version for an update check.

 

(Get-Item "C:\Program Files (x86)\checkmk\service\check_mk_agent.exe").VersionInfo.ProductVersion

[6Foot2]

Link: Windows 11 24H2 hoards 8.63 GB of junk you can't delete • The Register

 

Windows 11 24H2 users are finding there is undeletable data that remains on their devices after installing the recently released feature update.

 

The known issues list has not grown in the days since the rollout on October 15, however, for many users – this writer included – attempts to clean up the detritus after the update has left 8.63 GB of disk space occupied by "Windows Update Cleanup."

 

Having file remnants after a Windows update is not unusual, and, according to Microsoft, "Windows keeps copies of all installed updates from Windows Update, even after installing newer versions of updates." Space taken up by the old versions can be reclaimed – at least that's the idea...

 

... However, that 8.63 GB of data appears to persist regardless of how often a user attempts to delete it or restarts Windows 11. A scan of Microsoft's Feedback Hub confirms numerous users are affected ...

 

... The problem is that Windows 11 lists those files as old updates that the user can delete, even when the clean-up tools cannot remove the files. It is possible to remove them manually, but doing so could cause issues when the next set of updates arrive...

 

* My emphasis.

[kennysarmy]

 

On a test PC after updating to 24H2 we get this in the activation area of settings.

 

On a working PC still on 23H2 it says.

 

 

 

Anyone know what I might need to do on our AD to fix this?

[jthompson]

[ATTACH=CONFIG]72681[/ATTACH]

 

On a test PC after updating to 24H2 we get this in the activation area of settings.

 

On a working PC still on 23H2 it says.

 

[ATTACH=CONFIG]72682[/ATTACH]

 

 

Anyone know what I might need to do on our AD to fix this?

 

If it was an in-place upgrade, test whether you get the same error after a clean install of 24H2. If the clean install is okay, then I don't think you don't need to worry about fiddling with AD.

[kennysarmy]

If it was an in-place upgrade, test whether you get the same error after a clean install of 24H2. If the clean install is okay, then I don't think you don't need to worry about fiddling with AD.

 

Good plan.

[rossibIT]

On 26/11/2024 at 11:56, kennysarmy said:

 

On a test PC after updating to 24H2 we get this in the activation area of settings.

 

On a working PC still on 23H2 it says.

 

 

 

Anyone know what I might need to do on our AD to fix this?

Hi Kenny, 

Did you fix this? I am coming up with the same issue but with a different error code. I have cleaned build a couple of workstations and one is coming up with a digital license and the other is coming up with error code 0xC004F213 

Regards

Ross

[kennysarmy]

4 minutes ago, rossibIT said:

Hi Kenny, 

Did you fix this? I am coming up with the same issue but with a different error code. I have cleaned build a couple of workstations and one is coming up with a digital license and the other is coming up with error code 0xC004F213 

Regards

Ross

 

I think it resolved itself

[rossibIT]

As in yours is now showing as an organizational license? I have seen articles relating that it could take time to filter through to a workstation. Just not convinced it will resolve it. 

Ross