Cannot user experience deal with this while not tapping but scarcely the actual intermediate level of technical resource?

Question

Hi,

after an in-place reinstallation of Windows, an sfc/verify, it is apparent that a specific value in Registry is discarded by system on no legible prompt, like a reboot, but on random occasion; maybe a days time-out?

I mean the value in Game Configuration Store from the H/CurrentUser,

I 've queried MSLearn, and sent feedback and discussed it with GetHelp, and from my side I could justify that only for devices not set up by OEMs or expert users.

Which may be the case here, but how is it possible that specific value to behave like that? GameDVR_FSEBehaviour is quintessential to remain at (2), meaning disabled, because there it does not interfere with this device's BCD; but every some other time it doesn't even go to default, it is zeroed? Which is very risky for screen safety in fullscreen modes.

As this can be extemely discouraging to deal with, unless of course I keep open all of the time the 'regedt'' window and checking, which is what is going on since it has proved already useful once -is there not some instruction, or explanation to settle it?

Answer 1

Dear shifterworker880004

Thank you for posting in the Microsoft community.

Regarding your question about H/CurrentUser defining the current user's items, by default they shouldn't be modified, guess it might have something to do with the account profile that the user is using, for example, they define the GameDVR_FSEBehaviour effect on other devices, and then this setting is synchronized to the cloud through the account settings, and when logging in on the other device Automatically configuring the relevant settings has something to do with it.

GameDVR_FSEBehaviour alone, does not affect BCD.

A simple script can be written to monitor registry values and automatically restore them when changes are detected. For example, a PowerShell script can be used to periodically check and set values.

$key = "HKCU:\Software\Microsoft\Windows\CurrentVersion\GameDVR"  

$valueName = "GameDVR_FSEBehaviour" 

$desiredValue = 2 

while ($true) { 

    $currentValue = Get-ItemProperty -Path $key -Name $valueName -ErrorAction SilentlyContinue 

    if ($currentValue.$valueName -ne $desiredValue) { 

        Set-ItemProperty -Path $key -Name $valueName -Value $desiredValue 

        Write-Host "Value reset to $desiredValue" 

    } 

    Start-Sleep -Seconds 60 

}  =========================

Method 2: Use registry permission settings to prevent modifications

You can prevent regular unintentional modifications by changing the permissions of registry entries.

1. Open the Registry Editor:

Press Win + R, type regedit, and press Enter.

2. Navigate to a specific key:

Find HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\GameDVR.

3. Modify permissions:

Right-click on the GameDVR key and select “Permissions.

In the Permissions window, select the current user and then uncheck “Full Control” and “Write”. You can set the key to “Read Only”.

In this way, you can prevent user-level settings from being unintentionally changed by any process.

Disclaimer: Modifying the registry or workgroups is usually geared towards advanced users, administrators, and IT professionals, and it can help fix some problems, however, improper registry modifications can cause serious problems. Therefore, please make sure to strictly follow the steps below. For further protection, make a backup of the registry before modifying it. For more information on how to backup and restore the registry ref:

How to back up and restore the registry in Windows - Microsoft Support

Best Wish

Shawn.Z-MSFT | Microsoft Community Support Specialist