Windows 10 Upgrades Fails with ProfileUnity Client Installed

-
Since the beginning of Windows 10 in our company I have been stumped by failing Windows 10 Feature Updates...

It got the point (after spending 80-120 hours) that our upgrade process for Windows 10 to Windows 10 builds involved formatting the machines and reinstalling all software.  Needless to say, this was a major headache.

Since the release of 1709 for Semi-Annual Channel, my machine has failed to update multiple times and I decided I would submit myself to the pain and suffering of attempting to resolve it yet again.  

Windows update would show an error code of 0x80070057.  Most of the advice online says to reset windows update, delete SoftwareDistribution, etc.  I've tried all of that 100s of times before, so I went to find the setuperr.log file in the hidden directory on C.

In that log file I saw a bunch of errors (some below):
2018-01-30 01:11:49, Error                 CONX   0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]

2018-01-30 01:14:26, Error                 SP     SPMountWIMCallback: Error mounting/unmouting C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount\Windows\WinSxS\x86_microsoft-windows-b..d-bootfix.resources_31bf3856ad364e35_10.0.16299.15_en-us_bcf11044204a3379\bootfix.bin. GLE [87][gle=0x00000057]

2018-01-30 01:14:28, Error                 SP     CMountWIM::DoExecute: Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0x80070057[gle=0x00000057]

2018-01-30 01:14:28, Error                 SP     Operation failed: Mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim, index 1 to C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0x80070057[gle=0x000000b7]

The key part seems to be the inability to mount the WIM file... On a forum (https://www.sysnative.com/forums/windows-update-fixes-and-tutorials/20868-failed-mount-wim-file-c-windows-bt-sources-safeos-winre-wim-error-0x80070057.html), someone mentioned this might be related to a filter driver.  I ran the following command to list any filter drivers:

fltmc filters

This showed the ProfileUnity filter driver cbfltfs4, which ended up being the culprit of the failed upgrades!

How to fix it:

 Before attempting the upgrade, run:

sc  config  cbfltfs4  start= disabled

Run the Windows Upgrade normally

Renable the filter driver after the upgrade is complete by running:

sc  config  cbfltfs4  start= boot


Turns out this is highlighted in a recent ProfileUnity help article (https://liquidwarelabs.zendesk.com/hc/en-us/articles/115004142563-Windows-10-Feature-Update-via-SCCM-always-fails-when-ProfileUnity-client-is-installed)  talking about failed feature upgrades via SCCM.  Turns out the scope is much wider...

Comments

  1. DSF767November 27, 2019 at 3:22 PM

    Thank you so much! I have been beating my head against this for 2 days while trying to update my VDI image to 1909 and went though all the same steps you did until I googled the cbfltfs4 and saw your post.

    ReplyDelete

Post a Comment

Popular posts from this blog

Dell R740 issues with XenServer 7.1/7.2

-
Image
My last post talked about our new Dell R740s.  Response to that post have pointed out that there are a few things worth following up with since people have been having some issues with this server/Intel Gold 61xx Processors. I had a few minor issues getting XenServer installed, but mostly around storage and networking. *I should note that my servers are showing crash dumps in XenCenter, but everything is working perfectly.  Waiting on my support case to have those SSRs analyzed (case originally started to ask about support for the H740p card in XS7.2).  I will post and update when I hear back tomorrow morning. Storage Controller - H740p We went with the H740p card which is not supported on XenServer 7.2 (although support tells me it may be soon) so we had to go to 7.1.1 (7.1 CU1) and install the driver at  https://support.citrix.com/article/CTX226401 .  If you had to load this to detect disks, make sure you install it AGAIN at the end during supplemental...
Read more

Autodesk in Virtual Environments and What is "Allowed"

-
Yesterday at Autodesk University 2018, I attended a session (SD227281) that was supposed to be about "Best Practices for Virtualizing Your Autodesk Software."  What ended up happening was some sort of confusing and illogical announcement about new Terms and Conditions around what is allowed and what is not allowed in terms of licensing models for virtualized environments.  To categorize this session as devolving into an infuriating train wreck would be an accurate description. After cooling down and doing some research yesterday I am even more confused, and some of what we heard was seemingly wrong. First I'll summarize what was "announced" and what was discussed in that session by the two senior Autodesk people (John Looper and Chris Kayser). Announced in the presentation: Autodesk will permit virtualization for: - Subscriptions with single-user access - Enterprise Business Agreements - Server-based components (Think Autodesk Licensing Server...
Read more

NVIDIA GRID on Pascal - A Card Comparision

-
Image
I was all excited to post this, as I spent a decent amount of time on this subject leading up to ordering our new servers, and hadn't seen anyone else address it yet.  Then yesterday Jan Hendricks posted his thoughts on the subject which mirrored much of my findings ( https://jhmeier.com/2017/11/15/data-comparison-of-nvidia-grid-tesla-p4-and-p40/ ).  I guess that motivated me to finally finish my thoughts and get it posted as well! NVIDIA GRID 5.0 & Tesla Pascal Cards Photo Credit:  http://www.nvidia.com/object/accelerate-inference.html With NVIDIA GRID release 5.0 came support for Pascal GPUs.  While this brought many things (covered many other places), the most interesting part of this for me was that now ANY Tesla Pascal GPU works with NVIDIA GRID.  This opened us up to a wider array of options right away with 3 PCIe cards already generally available and an MXM option.  While NVIDIA pushed the P40 as the natural replacement for the M60, I w...
Read more