There are lot of Blog Posts and TechNet Articles which explain how to use Unified Write Filter (UWF) together with ConfigMgr. But most of them are written for older ConfigMgr Versions like 2007. Now I had a project with ConfigMgr 2012 R2 SP1 and we found some interesting things, which are not documented. All existing documentations will tell you, that you need to set some exclusions for ConfigMgr in UWF. But when you do this, then the Software Center won’t work and the following error message is displayed:
There is a problem showing the current status. More information: Loading Software Center returned error code 0x87D00244 (-2016411068).
You will find perhaps the following TechNet Forum Entry which explains the behavior and recommends to not create any ConfigMgr related exclusions. But when you follow this advice you get the following problem:
The Content will be downloaded before the computer reboots and UWF is disabled. After the reboot the application can’t be installed because the Content is not available. This means, you need to configure your ccmcache Folder as UWF exclusion to solve the issue. I also recognized that we need other exclusions:
uwfmgr File add-exclusion "c:\Windows\ccmcache" uwfmgr File add-exclusion "c:\_TaskSequence" uwfmgr File add-exclusion "c:\Windows\BootStat.dat"
Additionally I faced two other problems with UWF:
- ConfigMgr doesn’t enable UWF automatically after an Application Installation has finished. I tried different settings, sometimes it worked, but sometimes not. So I decided to use a Task Sequence. ConfigMgr disabled UWF before the Task Sequence starts and I could enable UWF again in the second last step of the Task Sequence.
uwfmgr.exe filter enable
In the last step we initiate a reboot of the Computer.
Tip: If you would like to prohibit logons to the client during Task Sequence, you can remove your user Accounts from the local User group and add them back after the servicing job is done, directly before the reboot is executed.
- My devices are domain joined and the devices should boot very fast. With this requirement I need my user profile generated before UWF is enabled the first time. So I enable UWF at the end of the OSD Task Sequence, but didn’t force a restart. I also set the Autologin for the primary user of this workstation. To have UWF enabled as fast as possible I wrote a short script which is executed when the first user is logged in and immediately reboots the computer.
I hope this tips will help you implementing UWF in your ConfigMgr environment.
- Microsoft Purview Information protect predefined permission groups demystified - February 28, 2023
- Extending Microsoft Sentinel with important device data - January 30, 2023
- SOC Monitor wall – Develop your Video Wall Application (Part 2) - August 22, 2022
Brandon · April 30, 2018 at 16:41
c:\Windows\BootStat.dat exclusion causing “Blue Screens Of Death” (BSOD) in our environment. Windows 10 1607 and 1709. Error “SYSTEM THREAD EXCEPTION NOT HANDLED” uwfs.sys
Marcel · September 14, 2018 at 07:26
Hi I am trying to accomplish this. Question about the Autlogon. You set the regkeys I presume to autologon with a specific account. Doesn’t the computer need a reboot after the Autologon TS step, to actually logon with the specified account? Can you share the Autologon script? Thanks.
Thomas Kurth · September 14, 2018 at 14:41
I have no longer access to the script. Yes, after the TS a reboot is initialized through the SMSTSPostAction variable.
Here you have a manual how to do this: https://www.petervanderwoude.nl/post/how-to-perform-an-action-directly-after-the-task-sequence-is-finished-with-configmgr-2012/