Windows 10: Differences between Compatibility Troubleshooter and registry key set

Hi all,
according to this tutorial
https://www.tenforums.com/tutorials/1...dows-10-a.html
compatibility settings could be done in several ways.

However, I'm experiencing a different behaviour if I set compatibility through registry key or through Program Compatibility Troubleshooter and I need some help about it.

I have a little application, written very long ago on a XP system, that uses an API for setting sound volume on mixer.
This API was no longer used in Windows 7, but running the program in compatibility mode was enough to make it work.
I made a script to set key in registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
and all went well.

Recently I went up with W10 and did the same. Executed the script and all done.
At this point I realized that memory limits were exceeded and resolved myself to recompile that program with updated API.
I went to regedit, deleted the key and retried to check memory (expecting the mixer call won't work).
Here my first surprise: it worked! and memory usage was still high!
It was as app was launched in compatibility mode, even if nothing was setted so. No key in Layers folder and no checkbox in Properties/compatibility Tab.

I then tried to use Compatibility Troubleshooter to see what it would have suggested; clicked on reccomended settings and it suggested no compatibility, tested app and BAM!
Second surprise, it doesn't work and low memory usage. Retried to launch it manually and same.

I tried several times and always the same effect applies.
It's like deleting keys in registry isn't enough to return to previous no-compatibility settings.

Does the Compatibility Troubleshooter set something different?
Or there's some key I'm missing?
Anyone else has experienced this?

Sorry for long post. I wanted to explain from the beginning, cause I'm still confused myself.

Thx
David

:)

 

Windows 10 Defer upgrade settings using Group Policy

I have my Windows 10 1607 and 1703 computers configured through Group Policy to have updates be applied according to Current Branch for Business. I also have group policy applied to set active hours between 7 am and 5 pm.

On the computers, under the registry key HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate ... The active hours show correctly with a start of "7" and end of "17". The BranchReadinessLevel is "20(32)" which translates to CBB.

However, the registry key HKLM\Software\Microsoft\WindowsUpdate\UX\Settiings ... The ActiveHoursStart is "8" instead of 7. The BranchReadinessLevel is "10(16)" Which translates to Current Branch.

If I open Settings, the settings for active hours and choosing the branch levels are
not greyed out and show hours of 8am to 5pm and a branch readiness level of "Current Branch".

I have 2 questions. 1. Why is the gui not displaying what I have applied through group policy?

2. What is the difference between the 2 registry keys? Why are their 2 different keys with conflicting settings?

Thank you in advance.

 

Difference between windows keys

The Microsoft Store sells retail, full version licenses for Windows 10 and you can download whatever architecture you want:

Buy Windows 10 Home/Pro

 

Hi, just wondering why you need to delve into the registry for this? You can set the compatibility mode manually via the GUI. (Besides using the troubleshooter).

 

Hi Dalchina,
I used to set registry key as a part of a setup script that set compatibility mode for some processes and a bunch of other stuff (the mixer process is only a part of a small suite that I distribute as gadget to some friends).
Anyway I want to avoid a user to have to manually check on compatibility checkboxes for every application I eentually develop in the future..

Anyway, I tried to reset compaatibility via the GUI but the effect is the same than removing registry key.

Troubleshooter makes something different and was wondering what it is.

I don't like very much this self-decided action from Windows, I'm worried it could hide something else.

 

Thanks for the explanation- maybe you can explain what difference you experience setting the compatibility (to the same setting?) those two ways. Hopefully someone might know more...