Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,468 questions
One value in registry the dvr_fsebehavior is prone to discard its set value for other than the default; what can bind it in place?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 26%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECD%3C/text%3E%3C/svg%3E)
Claus Debanker
41
Reputation points
hi,
it is highly important the value to remain at (2) not at default (1). Safety cooperates with bcdedit/set to permit fullscreen modes without risk of physical impact which can be extreme gradually & imperceptibly. However the value is discarded of its own at (0) on random occasions other than on a reboot or on another command line input with e.g. a global reset attribute.
It strikes as very unexpected for this to happen like that (at no obvious or detectable prompt).
The said value seems unique to alter in this manner; other safety values in 'regedt' do not do the same. For that matter I am not inclined to mention possible related previous courses that might have affected the registry -at any rate, they are unlikely to have done so (i.e. using a merge reg file for enabling/removing the processor frequency state in Power Settings? or a hypervisor machine to test Windows 11 enterprise on an non-qualified device?).
Urgently I request a workaround for this as I have communicated it also to Answer Desk. There has been no previous occasion where the System File Checker (sfc) was deemed to be settling such an issue.
Windows 10
Sysinternals
Sysinternals
Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
1,152 questions
{count} votes
-
Claus Debanker 41 Reputation points
2024-08-30T12:09:50.6766667+00:00 It can be noted that once after the Cumulative Update Preview for version 22H2 (KB5041582), at log-on the 'regedt' window showed for a few seconds the correct value for fse_behaviour, then moments later they were zeroed; it looks like this Windows update reboot to have been a g/shutdown, but on any other user's occasion for g/shutdown the specific values in registry were not altered.
(So this last incident is more like to condone the use of a script as suggested from another post.)
However, is it likely the registry be not aware of the BCD configuration in a way as to not toggle automatically the DVR setup? Or the other way round? If BCD is set up 'arbitrarily', the registry requires to assign a free policy to it?
Sign in to comment
Sign in to answer