Thanks Hellbovine im a noob in this but your guides are really useful. I hope with a lil more practice I can contribute to this blog.
Thank again!
Thank again!
Guide: Optimized Image
BKPB
Member
- Messages
- 81
- Reaction score
- 10
Hellbovine, I found a problem with one entry in the registry, in the file Reg_2_Security.reg.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel]
"MitigationOptions"=hex(3):20,22,22,00,00,02,00,00,00,02,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00
Perhaps this problem is only for me, but after making this entry in the registry, the Folder Marker v.3.2 program stops working for me.
The program stops running. Reinstalling the program doesn't help. Checked repeatedly. After deleting this entry from the registry, the program starts and runs. Please pay attention to this.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel]
"MitigationOptions"=hex(3):20,22,22,00,00,02,00,00,00,02,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00
Perhaps this problem is only for me, but after making this entry in the registry, the Folder Marker v.3.2 program stops working for me.
The program stops running. Reinstalling the program doesn't help. Checked repeatedly. After deleting this entry from the registry, the program starts and runs. Please pay attention to this.
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
I'll download that program and see if I can replicate it, but while I'm doing that it would be really helpful if you could use the following information to find the specific culprit on your computer too, that way we can see if we come to the same conclusion, in order to verify if the tweak or Folder Marker is at fault. If you look at the comments I put on that tweak it shows where those settings can be handled in the user interface.
Go to Start > Windows Security > App & browser control > Exploit protection settings. On an unmodified Windows installation all of these values will be set to "Use default (On)" in thier drop-down boxes. To troubleshoot this, start with the default settings on all 7 items, then reboot and run Folder Marker to see if the bug happens on that baseline, before we test anything else.
After that, go down the list starting with Control flow guard and disable it by setting it to "Off by default" and reboot the computer, then test Folder Marker again. Keep repeating this process until you make Folder Marker fail again or manage to get through the 7 available toggles. Skip "Data Execution Prevention (DEP)" testing though, because my guide doesn't modify that one. This situation can be tested and fixed on a live install, so there's no need to reinstall Windows unless you think there are other things that could be interfering.
Go to Start > Windows Security > App & browser control > Exploit protection settings. On an unmodified Windows installation all of these values will be set to "Use default (On)" in thier drop-down boxes. To troubleshoot this, start with the default settings on all 7 items, then reboot and run Folder Marker to see if the bug happens on that baseline, before we test anything else.
After that, go down the list starting with Control flow guard and disable it by setting it to "Off by default" and reboot the computer, then test Folder Marker again. Keep repeating this process until you make Folder Marker fail again or manage to get through the 7 available toggles. Skip "Data Execution Prevention (DEP)" testing though, because my guide doesn't modify that one. This situation can be tested and fixed on a live install, so there's no need to reinstall Windows unless you think there are other things that could be interfering.
HatsuFujiwara
New Member
- Messages
- 4
- Reaction score
- 0
Hey I'm just gonna ask a dumb question, I wonder if this guide will be updated for 24H2? Or this guide does not need an update because this guide is still applicable even for 24H2? Thank you for your wonderful guides btw, it helps a lot!
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
Good video, but that wasn't what I was asking for. Please read my reply again and get back to me. You skipped the entire third paragraph, which I gave explicit instructions on how to carry that out manually through the user interface, not through registry files. The point of this troubleshooting is to identify the actual culprit, because as I mentioned before and in the comments in that registry file, that one key handles multiple tweaks.
What I theorize might be the problem, is that you have perhaps an extra setting that I don't, and we need to do some steps to get to that answer. I will not be doing my half of the troubleshooting until you do yours first. I'm getting burned-out on the lack of cooperation from members lately, as evident by my next replies and the last few dozen I've made in recent months too. I'm not a mind reader, I need relevant information to solve problems.
There's a reason why helpers like myself, Txmmy (GamerOS), and others I won't speak for have stopped assisting on the forum as the years have progressed, and that is unfortunately accelerating at a rapid pace lately due to a ton of members posting complete nonsense and the most low effort posts I've seen to date. It's exhausting to say the least, and I've had my fill of it. It's not unreasonable for me to ask that minimal effort be applied.
Last edited:
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
The topic of W11 (23H2/24H2) has been inquired on dozens of times. I get where you're coming from in prodding me, but it's already answered and implied in several areas of my guide as well as in replies to this thread and other popular ones too. All my guides focus on W10, because I've proven that it's superior to W11 in terms of performance and stability (link). I did forget to add that link into my Optimized Guide though, so I apologize for my part in this--I'm spread thin, exhausted, and my to-do list is overwhelming, so I'm making mistakes like that now.
When I have free time I will get all my work updated, but the reality of the situation is there's no rush. The point of my work is for users to take the final release of W10 after Microsoft is done patching it, optimize it the best it possibly can be, and then use that golden image until W12 or something else is mature and worth migrating to later. W11's launch and evolution has been akin to Vista, and that's why the adoption rate is so low, because the world consensus is that it was a step in the wrong direction, which has been typical of every other Windows released by Microsoft.
Last edited:
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
I'm going to be frank with a general note here, based on problems I've dealt with this year from inexperienced members. For those that want to see future assistance and guide updates from me (if you don't care, please move on) then more effort needs to be put into requests for assistance. I've decided today to go into hibernation until I feel that the forum has returned to its senses. Keep in mind, the more time I spend assisting uncooperative people, which is all of my free time these days, is time taken away from updating my guides and it's a huge factor in the lack of updates.
Respect needs to be restored for the colossal number of hours and hard work that people like myself, Nuhi, Garlin, Txmmy, and so many others put into this forum and the tweaking community. Something you guys don't see, is the sheer number of silly direct messages people like us have to handle as well, and that's allegedly what caused the GamerOS (link1) to go defunct, so people need to pay attention. Anyone that wants to help me, can do so by stepping up, answering questions and trying to police (be respectful) their peers when it's appropriate to do so, such as on low effort posts.
What you guys don't seem to realize is that barely any of us old school, knowledgeable, computer guys exist anymore publicly, because we've all gotten burned-out by the short attention span of the TikTok generation full of Discord broscience, and we're sick of it. The following thread series is a perfect example of the absurdity (link2, link3, link4, link5) we've dealt with on this forum, which happens way too often these days.
I have a ton of grey hair in my beard already, which is entirely from my kids and the newbies on this forum. My point, and rhetorical question that I'd like our members to consider is this, "Who will innovate new tweaks and solve problems when we veterans are all gone?" We've seen how well it works out when the blind lead the blind on Discord, so have fun with that I guess...
Windows is only getting more complex, outmatching most enthusiasts nowadays. I'm trying to teach and pass on skills of how to learn to be self sufficient. Some people are very thankful, to which my respect goes out to those guys and I enjoy helping those types of people, but the lazy generation of today wants one of the most objectively difficult topics (computers) wrapped up in two sentences, so they complain about guides being too long, but then they complain it's too difficult when summarized--we helpers can't win.
I've done all I can (link6), by holding people's hands and walking them through, step by step, spoonfeeding the instructions so that it's idiot proof, but so many people have turned their brains off and can't even be successful when I'm saying, "Open up, here comes the choo choo train!" and shoving the answers down their throats. People used to read books and spends years in college or as a hobby to learn this stuff. In other words, it takes hard work and time--stop trying to bastardize it, and don't ask for advice if there's no intention to listen.
Respect needs to be restored for the colossal number of hours and hard work that people like myself, Nuhi, Garlin, Txmmy, and so many others put into this forum and the tweaking community. Something you guys don't see, is the sheer number of silly direct messages people like us have to handle as well, and that's allegedly what caused the GamerOS (link1) to go defunct, so people need to pay attention. Anyone that wants to help me, can do so by stepping up, answering questions and trying to police (be respectful) their peers when it's appropriate to do so, such as on low effort posts.
What you guys don't seem to realize is that barely any of us old school, knowledgeable, computer guys exist anymore publicly, because we've all gotten burned-out by the short attention span of the TikTok generation full of Discord broscience, and we're sick of it. The following thread series is a perfect example of the absurdity (link2, link3, link4, link5) we've dealt with on this forum, which happens way too often these days.
I have a ton of grey hair in my beard already, which is entirely from my kids and the newbies on this forum. My point, and rhetorical question that I'd like our members to consider is this, "Who will innovate new tweaks and solve problems when we veterans are all gone?" We've seen how well it works out when the blind lead the blind on Discord, so have fun with that I guess...
Windows is only getting more complex, outmatching most enthusiasts nowadays. I'm trying to teach and pass on skills of how to learn to be self sufficient. Some people are very thankful, to which my respect goes out to those guys and I enjoy helping those types of people, but the lazy generation of today wants one of the most objectively difficult topics (computers) wrapped up in two sentences, so they complain about guides being too long, but then they complain it's too difficult when summarized--we helpers can't win.
I've done all I can (link6), by holding people's hands and walking them through, step by step, spoonfeeding the instructions so that it's idiot proof, but so many people have turned their brains off and can't even be successful when I'm saying, "Open up, here comes the choo choo train!" and shoving the answers down their throats. People used to read books and spends years in college or as a hobby to learn this stuff. In other words, it takes hard work and time--stop trying to bastardize it, and don't ask for advice if there's no intention to listen.
Last edited:
BKPB
Member
- Messages
- 81
- Reaction score
- 10
When I wrote that everything works fine with manual settings, I meant that (I completed the entire third paragraph) I turned each item on and off and rebooted the computer every time.
I totally agree with you. Most users come here to get a quick answer to their question and move on with their business. At the moment, I probably also belong to such people. I understand you very well, it is difficult to spend a huge amount of time in your personal life and see that others only want you to do the work instead of them. Personally, I am grateful for your work.
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
Thank you, and yeah that's why it's confusing, because I couldn't know if you did follow the third paragraph, since there was a lack of details provided. If people aren't explaining to me what they are and aren't doing, then I can't follow along and help, since I'm just fumbling in the dark. If anyone here put their computer literally in front of me, I could fix it within minutes or hours in almost all cases, because I'm getting feedback on what's happening and then I can make better choices on how to proceed. I can't do that on the NTLite forums though, when people give us little to no information.
So based on what I've read, the registry file installation breaks the folder program, while deleting the key fixes it. We also know that manually toggling the user interface doesn't cause the same problem. That says to me the issue is either the registry file you are using to install the tweak has some kind of incorrect parameter or your MitigationOptions key is different than mine in a way that makes them incompatible between our computers.
TROUBLESHOOTING STEPS
1) To solve this next dilemma, please upload the original file you used in the video to break the folder program with. I can analyze it to see if there's something that is causing it to fail. If you don't have the original file, just let me know and then proceed to the next step.
2) Delete the MitigationOptions key from the registry and reboot. Now, go into the security user interface again and toggle all 7 of those settings to their defaults if they aren't reset again, and reboot if you needed to make any changes. Now open regedit and export the MitigationOptions key while your security user interface shows everything set to the defaults. Upload that file, and then I will compare it to my computer and analyze that.
3) Please look at the comments I wrote on that tweak inside my registry file and compare those notes to how your security user interface appears. Do we have all the exact same settings in the same order from top to bottom? Do you have any additional settings or notice anything that differs?
4) Type "winver" inside a Run box or Command Prompt, without the quotes. It should open a box that lists the Windows build, please let me know the full build number shown there and operating system used.
2) Delete the MitigationOptions key from the registry and reboot. Now, go into the security user interface again and toggle all 7 of those settings to their defaults if they aren't reset again, and reboot if you needed to make any changes. Now open regedit and export the MitigationOptions key while your security user interface shows everything set to the defaults. Upload that file, and then I will compare it to my computer and analyze that.
3) Please look at the comments I wrote on that tweak inside my registry file and compare those notes to how your security user interface appears. Do we have all the exact same settings in the same order from top to bottom? Do you have any additional settings or notice anything that differs?
4) Type "winver" inside a Run box or Command Prompt, without the quotes. It should open a box that lists the Windows build, please let me know the full build number shown there and operating system used.
Last edited:
BKPB
Member
- Messages
- 81
- Reaction score
- 10
The order in my file has been changed. When I use your original file, the result is the same (my program does not start).
It may be related to my other registry files. I can't track it, it will take a long time.
I just excluded this registry key and everything works fine.
If this does not cause errors for you, then my registry settings conflict 100% and you do not need to look for an error.
Link to a program that doesn't start after applying the registry file.
https://www.thewindowsclub.com/starter-startup-manager-windows
I had no complaints about your settings, I just wanted to let you know that this happened to me.
I didn't think it could cause a conflict because of my settings. and added a lot of extra work to you.
I should have thought about it first.
It may be related to my other registry files. I can't track it, it will take a long time.
I just excluded this registry key and everything works fine.
If this does not cause errors for you, then my registry settings conflict 100% and you do not need to look for an error.
Link to a program that doesn't start after applying the registry file.
https://www.thewindowsclub.com/starter-startup-manager-windows
I had no complaints about your settings, I just wanted to let you know that this happened to me.
I didn't think it could cause a conflict because of my settings. and added a lot of extra work to you.
I should have thought about it first.
Attachments
Last edited:
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
I need to wrap this up, so I can start working on my own image and guides again. I jumped ahead and solved it:
Instead of testing this on my older desktop as I usually do, I got onto my modern laptop and checked the registry and settings to make sure there wasn't anything new that my desktop didn't have. They were the same though, and they both use my Optimized Image guide exactly as it's written. Both machines are currently using the W10 22H2_V1 ISO from Microsoft for the base.
1) Neither of the programs you asked about support Windows 8/8.1/10/11...The Folder Marker v3.2 program was released in 2011 and only supports Windows 7 and below. The Startup program v5.6.2.9 is even older, released in 2009 and is for Vista and below. Old programs are prone to issues on new operating systems, so updating the program or using a modern alternative should be the first course of action.
2) If you're using pirated sources, it's probably where some of the issues are coming from. Only use official sites to download programs like I did, and you'll probably see different results. Folder Marker v3.2 worked just fine, and so does Startup v5.6.2.8. However, Startup v5.6.2.9 fails to launch, but that's something the developer needs to fix, so you'll have to contact them. Malware in pirated versions could be interfering too.
3) Other potential sources that cause issues like this are bad UAC tweaks--only use the UAC tweaks from my guide, as those are safe and still get rid of the UAC nag messages. Component removals may also be at fault, or Windows permissions that were modified. Try running programs by double left-clicking, but then also try right-clicking and using the administrator option. Lastly, try turning off "Realtime protection" in Defender.
Summary: Operator error, piracy, outdated programs, or bad tweaks are the likely culprits here.
1) Neither of the programs you asked about support Windows 8/8.1/10/11...The Folder Marker v3.2 program was released in 2011 and only supports Windows 7 and below. The Startup program v5.6.2.9 is even older, released in 2009 and is for Vista and below. Old programs are prone to issues on new operating systems, so updating the program or using a modern alternative should be the first course of action.
2) If you're using pirated sources, it's probably where some of the issues are coming from. Only use official sites to download programs like I did, and you'll probably see different results. Folder Marker v3.2 worked just fine, and so does Startup v5.6.2.8. However, Startup v5.6.2.9 fails to launch, but that's something the developer needs to fix, so you'll have to contact them. Malware in pirated versions could be interfering too.
3) Other potential sources that cause issues like this are bad UAC tweaks--only use the UAC tweaks from my guide, as those are safe and still get rid of the UAC nag messages. Component removals may also be at fault, or Windows permissions that were modified. Try running programs by double left-clicking, but then also try right-clicking and using the administrator option. Lastly, try turning off "Realtime protection" in Defender.
Summary: Operator error, piracy, outdated programs, or bad tweaks are the likely culprits here.
Last edited:
tired-it
Member
- Messages
- 172
- Reaction score
- 18
Whenever you have time, I'd be curious to read about the issues Microsoft fixed, the ones that you were waiting for them to address. I have been somewhat in the loop regarding some longstanding bugs with Windows, but my recent focus on Windows 11 has distracted my time away from any new Windows 10 developments.
audiobabble
New Member
- Messages
- 21
- Reaction score
- 7
Hello, me again!
Was looking through the .reg files and noticed the Windows Update 'pause' is set for 4 years from 2022... meaning it will be un-paused in January 2026?
I'm guessing there must be some kind of maximum value for the number of days pause... otherwise, why not set it to 100 years in the future?
I went and changed mine to 2028... but then an odd thing happened.... I started getting updates installing themselves, even though Update tells me it is paused until 2028. Fairly sure I did it correctly, kept the 4-year maximum and put in a start date of 2024. Very strange.
Actually, if I remember correctly, one update installed itself before having changed any registry entries. The one thing I did was to check to see if Windows Update had a 'paused until' date in settings (which I don't think it did.. it was just blank -- again: IRRC). This somewhat stretches credibility but it's as if just by opening Windows Update settings, I 'awoke the beast'!
I've restored a partition backup from before I messed around with the registry setting and am waiting now to see if it happens again.
[EDIT] so, yes after going online for a bit, I find a bunch of updates ready to install...
On checking, I've found that for some reason the PauseFeatureUpdates/PauseQualityUpdates start/end time reg entries have disappeared. I definitely did not do that. Of course, I've re-instated them now, but will be keeping an eye on it.
Was looking through the .reg files and noticed the Windows Update 'pause' is set for 4 years from 2022... meaning it will be un-paused in January 2026?
I'm guessing there must be some kind of maximum value for the number of days pause... otherwise, why not set it to 100 years in the future?
I went and changed mine to 2028... but then an odd thing happened.... I started getting updates installing themselves, even though Update tells me it is paused until 2028. Fairly sure I did it correctly, kept the 4-year maximum and put in a start date of 2024. Very strange.
Actually, if I remember correctly, one update installed itself before having changed any registry entries. The one thing I did was to check to see if Windows Update had a 'paused until' date in settings (which I don't think it did.. it was just blank -- again: IRRC). This somewhat stretches credibility but it's as if just by opening Windows Update settings, I 'awoke the beast'!
I've restored a partition backup from before I messed around with the registry setting and am waiting now to see if it happens again.
[EDIT] so, yes after going online for a bit, I find a bunch of updates ready to install...
On checking, I've found that for some reason the PauseFeatureUpdates/PauseQualityUpdates start/end time reg entries have disappeared. I definitely did not do that. Of course, I've re-instated them now, but will be keeping an eye on it.
Last edited:
PerhapsAverage
New Member
- Messages
- 22
- Reaction score
- 1
Currently in the process of doing so. Things shouldn't break but even if they do they will not have been used regardless (bloatware, telemetry, etc).
I do expect for many reg keys to not work, reducing the impact that the guide makes on the system overall. Should still work anyways.
Specifying a TargetReleaseVersion will prevent this warning, because WU understands you don't care about upgrading to another release.
The real reason for this warning is CompatAppraiser task has flagged this PC. Open regedit and look for this key:
Code:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators1. Remove the right subkey for your OS.
2. Delete the scheduled task which creates this key:
Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
But listing TargetReleaseVersion is the simplest method.
Does anyone know any permanent fix for this? Or a way to enforce it?
I have applied the power settings reg file, but I am having this issue on some desktop machines that use motherboards with integrated CPU's (just like notebooks), in other words, I go to control panel to check the power settings and when I go to the "choose what the power button does", the "when I press the power button" is set to SLEEP instead of SHUT DOWN.
This only happens on some machines that have motherboards with integrated CPU's, on most installations it's working properly, and the power button is set to shut down, instead of sleep when I got to check it after first boot.
I have applied the power settings reg file, but I am having this issue on some desktop machines that use motherboards with integrated CPU's (just like notebooks), in other words, I go to control panel to check the power settings and when I go to the "choose what the power button does", the "when I press the power button" is set to SLEEP instead of SHUT DOWN.
This only happens on some machines that have motherboards with integrated CPU's, on most installations it's working properly, and the power button is set to shut down, instead of sleep when I got to check it after first boot.
Hellbovine
Well-Known Member
- Messages
- 1,183
- Reaction score
- 726
Here's my previous discussions (link1, link2) on power overrides, but the gist of what's happening is that Windows automatically adds up to 4 different registry keys in multiple places, depending on the power capabilities of the hardware in use, when the operating system is first installed.
The tweaks will show up as one of the following key names in Regedit:
- OverrideACSettingIndex
- OverrideDCSettingIndex
- ProvACSettingIndex
- ProvDCSettingIndex
When these keys appear in the \Power\ branch of the registry, they act like a group policy and take priority over the user's settings as well as the operating system defaults. To stop that behavior, simply delete any keys with the names shown above and the operating system will go back to using the values from the standard keys that are labeled plainly as "ACSettingIndex" and "DCSettingIndex" without the "Override" or "Prov" prefixes.
The tweaks will show up as one of the following key names in Regedit:
- OverrideACSettingIndex
- OverrideDCSettingIndex
- ProvACSettingIndex
- ProvDCSettingIndex
When these keys appear in the \Power\ branch of the registry, they act like a group policy and take priority over the user's settings as well as the operating system defaults. To stop that behavior, simply delete any keys with the names shown above and the operating system will go back to using the values from the standard keys that are labeled plainly as "ACSettingIndex" and "DCSettingIndex" without the "Override" or "Prov" prefixes.
Last edited: