G
Gerhard1969
Guest
Hello on Windows 10 Enterprise 1809 and Windows 10 Enterprise 2019 LTSC the UWF crash with the following 4 Steps reproduceable.
Execute Cmd as Admin:
-uwfmgr filter enable
-uwfmgr volume protect all
Reboot the system
Execute Cmd as Admin:
-uwfmgr filter disable
Reboot the system
Execute Cmd as Admin:
-uwfmgr filter reset-settings
After that the uwf crashes with the following message:
Error: Could not reset UWF Settings (Access is dienied)
From this point which each other uwfmgr command you get the same error, and it is not useable anymore!
It is also not possible to repair this behavior by disable "Unified Write Filter" under "Turn Windows feature on or off" in "Device Lockdown" group and enable it under a reboot again.
The error message above still occurs again.
This behavior is reproduceable with Windows 10 Enterprise 1809 and Windows 10 Enterprise 2019 LTSC also with the latest QFEs (Build 17763.194)
It can also reproduced in Hyper-V with Windows 10 Enterprise Evaluation Build 17764.rs5_release.180914-1434
With Windows 10 Enterprise 1803 this things works without any problems.
You can verify this also in Hyper-V with Windows 10 Enterprise Evaluation Build 17134.rs4_release.180410-1804
Please bring us as fast as possible a fix for this heavy bug!
More...
Execute Cmd as Admin:
-uwfmgr filter enable
-uwfmgr volume protect all
Reboot the system
Execute Cmd as Admin:
-uwfmgr filter disable
Reboot the system
Execute Cmd as Admin:
-uwfmgr filter reset-settings
After that the uwf crashes with the following message:
Error: Could not reset UWF Settings (Access is dienied)
From this point which each other uwfmgr command you get the same error, and it is not useable anymore!
It is also not possible to repair this behavior by disable "Unified Write Filter" under "Turn Windows feature on or off" in "Device Lockdown" group and enable it under a reboot again.
The error message above still occurs again.
This behavior is reproduceable with Windows 10 Enterprise 1809 and Windows 10 Enterprise 2019 LTSC also with the latest QFEs (Build 17763.194)
It can also reproduced in Hyper-V with Windows 10 Enterprise Evaluation Build 17764.rs5_release.180914-1434
With Windows 10 Enterprise 1803 this things works without any problems.
You can verify this also in Hyper-V with Windows 10 Enterprise Evaluation Build 17134.rs4_release.180410-1804
Please bring us as fast as possible a fix for this heavy bug!
More...