It's a bit confusing, but my registries are correct. You're focusing on "SettingValue" which isn't relevant here. If you want to change an AC/DC value, it needs to match the number written on the actual yellow folders you drew red arrows on.

Let's do a hands-on example. Open regedit and navigate here: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\9596FB26-9850-41fd-AC3E-F7C3C00AFD4B\03680956-93BC-4294-BBA6-4E0F09BB717F\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e

This is for adjusting media playback in the power plans, and is pointing to the default settings for the Balanced plan. Microsoft set my Balanced plan to a value of "1" for AC, which means it uses "Prevent idling to sleep" while on continuous power, but has a value of "0" for DC, which means it uses "Allow the computer to sleep" while on battery power.

If you were correct, the values for the Balanced plan would use "80000001" for ACsettingindex and "80000000" for DCsettingindex, but Microsoft doesn't do that. Also, if you click on the yellow "2" folder, you'll notice the "SettingValue" is "80000041" and if you wanted to use "Allow the computer to enter Away Mode" which is what that folder handles, then we need an AC/DC settingindex of "2" instead of whatever "SettingValue" has.

Lastly, it's really easy to just test stuff like this before posting. Simply install the "80000041" value from the last paragraph and watch how it fails in the Control Panel. According to your theory it should set my Balanced power plan to "Allow the computer to enter Away Mode" but it actually bugs out the display page and it shows no options, meaning that setting is now broken.
 
Last edited:
It's a bit confusing, but my registries are correct. You're focusing on "SettingValue" which isn't relevant here. If you want to change an AC/DC value, it needs to match the number written on the actual yellow folders you drew red arrows on.

Let's do a hands-on example. Open regedit and navigate here: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\9596FB26-9850-41fd-AC3E-F7C3C00AFD4B\03680956-93BC-4294-BBA6-4E0F09BB717F\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e

This is for adjusting media playback in the power plans, and is pointing to the default settings for the Balanced plan. Microsoft set my Balanced plan to a value of "1" for AC, which means it uses "Prevent idling to sleep" while on continuous power, but has a value of "0" for DC, which means it uses "Allow the computer to sleep" while on battery power.

If you were correct, the proper registry values for the Balanced power plan would use "80000001" for ACsettingindex and "80000000" for DCsettingindex, but that isn't the case and we can see it on a default Windows install. Also, if you click on the yellow "2" folder in this example, you'll notice the "SettingValue" is "80000041" but if you actually wanted to use "Allow the computer to enter Away Mode" then it needs an ACsettingindex of "2" as the "SettingValue" is not what we are targeting.

Lastly, it's really easy to just test stuff like this before posting. Simply install the "80000041" value from the last paragraph and watch how it fails in the Control Panel. According to your theory it should set my Balanced power plan to "Allow the computer to enter Away Mode" but it doesn't. Instead, it bugs out the Control Panel and it shows nothing set at all, meaning that option is now broken.
Oh, i see, now i get it. In *.reg files you have to set the "index", not the "value". The Value will be set automatically by windows.

1709064830250.png

Thank you for explaining this to me in such detail!
 
I just finished installing a custom LTSC 2021 image using your script. Almost everything went flawless except that the night light does not work. I can enable or disable it, move the intensity cursor, but it has no effect on my screen lightning color. Has anyone experienced that before ?
 
Last edited:
Are you able to attach the extra tweaks you added, so I can review those to see if I can help find the problem? Also, have you tested an unmodified install of the build you are using to see if it's a Windows or driver bug? On that note, did you install a graphics driver yet?
 
I also support the notion that HP Support Assistant is garbage. It was forcibly installed on my laptop by Windows Update when I was testing things after I bought it, and every reboot would then throw an error message until I uninstalled that software.

Drivers are a big issue with laptops as a whole, because they tend to get many extra drivers and optional junk that equivalent desktop hardware doesn't. For example, the HP website says I need like 20 drivers, when the reality is only half or less are actually mandatory, the rest are usually adding more potential for bugs, resource usage, DPC latency, and telemetry, for little to no usefulness in return.
 
I also support the notion that HP Support Assistant is garbage. It was forcibly installed on my laptop by Windows Update when I was testing things after I bought it, and every reboot would then throw an error message until I uninstalled that software.

Drivers are a big issue with laptops as a whole, because they tend to get many extra drivers and optional junk that equivalent desktop hardware doesn't. For example, the HP website says I need like 20 drivers, when the reality is only half or less are actually mandatory, the rest are usually adding more potential for bugs, resource usage, DPC latency, and telemetry, for little to no usefulness in return.
Hi,

Loving everything so far, however.

One of your registry files is causing my game to crash, I'm trying to test one at a time, but it's really time consuming testing each one.

So I'm playing Helldivers 2 on Steam, the game loads, I press play, anytime It begins to play it crashes.

Any ideas?

Sam
 
I worked out it's registry file 6.

Anytime I leave it out, it's fine, anytime I include it, some of games crash.

Also with file 3, when I restart my computer I get an Explorer.exe error.
 
I worked out it's registry file 6.

Anytime I leave it out, it's fine, anytime I include it, some of games crash.

Also with file 3, when I restart my computer I get an Explorer.exe error.
It would help to know the exact version of Windows that you are on. Those registry files have been fairly solid on the intended Windows 10 version and may require tweaks on a different build. File 3 is where the bulk of the settings are, but as far as I can tell, most if not all of those settings can be found by just browsing system settings. File 6 has a few miscellaneous settings, but it shouldn't crash games.
 
It would help to know the exact version of Windows that you are on. Those registry files have been fairly solid on the intended Windows 10 version and may require tweaks on a different build. File 3 is where the bulk of the settings are, but as far as I can tell, most if not all of those settings can be found by just browsing system settings. File 6 has a few miscellaneous settings, but it shouldn't crash games.
Oh sorry I'm on 11 Pro.

For some reason I can't add a new Bluetooth device to connect my wireless controller. Not sure if that's a component I've removed.
 
...For some reason I can't add a new Bluetooth device to connect my wireless controller. Not sure if that's a component I've removed.
There's too much going on here, you mentioned a game crashing, explorer errors, and now bluetooth, with component removals too. Major issues like these are usually due to file dependencies caused by removals, so those need to be isolated and tested. In other words, to test a scenario that has multiple problems, the best approach is to isolate and troubleshoot the main layers:

1) Test an unmodified Windows and see if problems appear. If yes, then it's Microsoft's fault.
2) Test a custom image with only component removals, nothing else, and see if problems appear. If yes, which removal causes it?
3) Test a custom image with only my guide, nothing else, and see if problems appear. If yes, which tweak causes it?
 
Last edited:
There's too much going on here, you mentioned a game crashing, explorer errors, and now bluetooth, with component removals too. Major issues like these are usually due to file dependencies caused by removals, so those need to be isolated and tested. In other words, to test a scenario that has multiple problems, the best approach is to isolate and troubleshoot the main layers:

1) Test an unmodified Windows and see if problems appear. If yes, then it's Microsoft's fault.
2) Test a custom image with only component removals, nothing else, and see if problems appear. If yes, which removal causes it?
3) Test a custom image with only my guide, nothing else, and see if problems appear. If yes, which tweak causes it?
Hi,

Thank you for your reply, I am slowly working through this.

I have made a lot of boot files onto a yubi, and so far registry 6 the last one always causes my games to crash.
 
I dunno...
Code:
; Start > Xbox Game Bar > Settings > Show tips when I start a game > Off
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\GameBar]
"ShowStartupPanel"=dword:00000000

You can disable this online with:
reg add "HKEY_CURRENT_USER\SOFTWARE\Microsoft\GameBar" /v ShowStartupPanel /t REG_DWORD /d 1 /f
 
I have made a lot of boot files onto a yubi, and so far registry 6 the last one always causes my games to crash.
Is the YubiKey just for login authentication or are you doing something else? Googling Helldivers 2 gives tons of results for game crashes, which means it's unlikely to be an NTLite or tweaking problem. The game was just released on February 8th, and the expectation is that major bugs will plague every game for the first 12 months, since shareholders push unfinished games out to consumers nowadays and fix it later with patches.

You don't have to make new images and reinstall Windows to test registry files. Instead, edit the file you think is the problem and change the 00000000 values into 00000001 to enable them. That won't work for absolutely every key, but it will for most, and the rest you can google the key's name to figure those out. Then save your edits, exit the file, double-click it to install, reboot, and test the issues again.
 
Last edited:
Back
Top