Fields added in the Wallpaper policy for lockscreen not displaying properly on windowsSolved

I ran into something like this before, though I didn’t use the policy. Image was zoomed out in the lock screen. It actually was because an option called “Make the lock screen image react when I move my PC” (Settings > personalization > lock screen) is turned on in your devices. 

It’s basically like the background motion feature for the lock screen image. When enabled, the image will slightly pan or move in response to your device’s physical movement, creating a dynamic effect. 

Thank god, got a solution for this issue. It works. 
Something I’ve noticed is that on my personal laptop, it doesn’t seem to have that option.

That option is only available on Windows 10/11 devices which have an accelerometer. 
If your device doesn’t have it, the setting won’t show up. 
As for Surface pro, it does have one.

Okay, I was wondering if there’s an option in Hexnode that I can use to disable this feature on our devices, cause manually going to each device and disabling it is quite a hassle. 
There are quite a number of devices too.

I don’t think hexnode currently has any restriction for that, as far as I know.

But you can run a script that disabled it through Hexnode.

You can use this script:

Make sure to restart the device after execution. I think you can trigger a bulk restart from Hexnode too.
After that, this option will no longer appear in the settings.

And if you want to re-enable it, just change the value of $valueData to 0 and re-run the script.

Much appreciated.

Hey there, 
I’m the IT admin at my company. I used the script to disable the feature, and it disappeared from the device. 

But after running the script to re-enable it (yes, I changed the value to 0 and even restarted the device), it doesn’t get enabled again or the option doesn’t seem to come back. 

I had a similar encounter, not with this particular option, but I had to create a new registry key for something else.
Changing the value didn’t work, but what worked for me was deleting the registry entry and restarting the device.

Try this one-liner script:

I think this should work.

Thanks a lot, the option came back. You really saved me on this one.