Category Archives: Copilot+ PCs

Copilot+ PCs, Device drivers, Insider stuff, Recent Activity, WED Blog, Windows 11

Dxdiag Shows WDDM Version Info

4 Comments

Just recently, I’ve seen coverage that proclaims a new Windows Display Driver Model (aka WDDM) is available as version 3.2. That said, it’s currently supported only in Copilot+ PCs running Windows 11 24H2. Since I happen to have one, I wanted to check to see if I needed to update that manually, or if WU/install had done so already. That’s how I learned that the Direct X Diagnostic Tool, aka Dxdiag shows WDDM version info on Windows PCs. You can see the output that confirms 3.2 is running as the lead-in graphic above.

Confirmed: Dxdiag Shows WDDM Version Info

Just for grins, I also ran the diagnostic tool on my Lenovo ThinkPad P16 Gen 1 Mobile Workstation. (Hint: to do that, enter Winkey+R to open the run box, type “dxdiag,” then click Enter.) It’s running Windows 11 23H2 (Build 22631.3958). According to the great ElevenForum.com tutorial from uber-tut-master Shawn Brink “Find WDDM Version in Windows 11” it should be running version 3.2. Yet dxdiag shows 3.1 as you can see here:This is more in keeping with the WindowsLatest story that clued me into this version upgrade’s availability. And indeed, Copilot confirms that it only runs on version 24H2, not on 23H2 (as the afore-linked ElevenForum tutorial asserts). I think I’ll shoot Brink a message to ask for his opinion on this apparent discrepancy. Stay tuned!

But Wait…There’s More!

For further grins, I checked one of my Insider Preview Canary Channel PCs right now, and observed that:

  • This version is part of the 24H2 family (Build 26257.5000)
  • It is not a Copilot+ PC (Intel 8th Gen/Tiger Lake i7-1180G7)
  • It also runs WDDM 3.2, as you can see here:

To me, this indicates pretty unequivocally that 24H2 is the way to get WDDM 3.2. Thus, it shows up on older PCs running 24H2 in the Insider Preview family tree, as well as newer ones with 24H2 pre-installed (right now, that’s only Copilot+ PCs). Go figure!

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

24H2 Adopts Energy Saver

Leave a comment

Battery Saver is out, and Energy Saver is in for Windows 11 version 24H2. You can see the new power management capability in Settings > System > Power & Battery in Build 26100 on Copilot+ PCs. For example, see the top elements in the lead-in graphic. When 24H2 adopts Energy Saver, this does come with some behavioral changes, too. Read on for more info and an MS Learn link.

When 24H2 Adopts Energy Saver, Then What?

Good question, and one that MS addresses directly in an MS Learn article entitled Energy Saver (dated 6/24/2024). Basically Energy Saver kicks in at a certain level of remaining battery capacity, and restricts Windows 11’s ordinary behaviors to — wait for it — save energy. Note: here’s a shout-out to Mayank Parmar at Windows Latest for bringing this to my attention.

Energy Saver Particulars

Check out the MS Learn article for all the details, but here’s a thumbnail summary of how Energy Saver works:

1. It kicks in when remaining charge levels dip to a certain level. It’s user-settable, and defaults to 30% (see lead-in graphic).

2. Users can turn Energy Saver on or off via Quick Settings in the system tray as needed. MS recommends enabling Energy Saver all the time. It can even be set to work when a laptop is plugged into AC.

3. When Energy Saver is on, users cannot change power mode in Settings. Display brightness is reduced by 30% (users can toggle this setting, and OEMs can alter this value). Transparency effects for window backgrounds are disabled.

4. For unplugged devices with charge levels below the energy saver threshold, these other behaviors will manifest:

a. MS apps — e.g. OneNote, OneDrive, Phone Link, and so forth — may not sync to save energy.

b. Background apps will not run in the background unless specifically enabled. Certain app categories are exempted (e.g. VoIP) to preserve communications.

c. Non-critical Windows update downloads are blocked, but update scans still occur.

d. Telemetry is (mostly) blocked except for critical items (e.g. census data).

e. Task scheduler ignores IdleSettings and MaintenanceSettings, and runs tasks only if a user is logged on.

For all the details, please consult the MS Learn article. This will change how Windows behaves when PCs update to 24H2 and beyond, so these alterations are worth pondering. For further details on energy saver status tracking see the MS Learn item for SYSTEM_POWER_STATUS. Cheers!

Facebooklinkedin
Facebooklinkedin