{"id":2114,"date":"2017-01-22T22:07:26","date_gmt":"2017-01-22T21:07:26","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=2114"},"modified":"2022-06-23T20:58:16","modified_gmt":"2022-06-23T18:58:16","slug":"windows-10-error-0x80070057-from-cloudfogger","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/01\/22\/windows-10-error-0x80070057-from-cloudfogger\/","title":{"rendered":"Windows 10: Error 0x80070057 from Cloudfogger"},"content":{"rendered":"

[German<\/a>]Some users are receiving error 0x80070057 during distinct Windows 10 operations (backup, system restore, upgrades). Recently I stumbled upon Cloudfogger as a root cause for this error code. Here are a background information about this case.<\/p>\n

<\/p>\n

\"\"Users of Windows 10 are facing many errors caused by outdated software. The source of this problem is \"Windows as a service\" \u2013 the operating system will be upgraded two or three times a year. In best case, a software refuse to run (this was the case with StarMoney 9 in Windows 10 Version 1607).<\/p>\n

Non compatible software as a show stopper<\/h3>\n

In worst case, a feature upgrade stalls with an error or is refused due to an non compatible app. Sometimes setup.exe <\/em>provided in install media (created via Media Creation Tool) warns and recommends to uninstall app xyz. But in some cases the message is pretty cryptically \u2013 as\u00a0 show below.<\/p>\n

\"Windows<\/p>\n

We have a recommendation to uninstall an app, but the app isn't named. I have covered this case within my blog post Windows 10 Anniversary Update: inkompatible Apps (VPC)<\/a>, and I discussed, how to identify the app manually.<\/p>\n

In a really bad case, the setup wizard doesn't drop a warning, and a feature upgrade or an update installation stalls with error 0x80070057 (E_INVALIDARG, or ERROR_INVALID_PARAMETER). The error message doesn't deliver a clue what went wrong.<\/p>\n

Technical details (behind the curtains)<\/h3>\n

Some third party system tools are installing filter drivers within Windows, that are hooking system calls. Those filter drivers are passing parameters to the next sibling within the filter driver chain.<\/p>\n

I interpret error code 0x80070057 (ERROR_INVALID_PARAMETER) in a manner, that a filter driver is hooked into file system calls. And the filter driver handler doesn't passes the parameters in a right manner to the next filter driver. Then an upgrade install, or accessing volume shadow copies (VSS) during system restore or backup fails with error code 0x80070057 (ERROR_INVALID_PARAMETER).<\/p>\n

Log file analysis is difficult<\/h3>\n

We can check the log files written during an upgrade installation (I've discussed this within my German blog post Windows 10: Protokolldateien bei Upgrade-Fehlern analysieren<\/a>, a few hints are also discussed here Windows 10: Analyze upgrade errors<\/a>). But it's difficult. Therefore I suggest within my blog post, to uninstall tools like third party antivirus software, system tools, TuneUp etc. and roll back all settings mode within those tools. Also you should clean the system from registry entries and files left from these tools after uninstalling them.<\/p>\n

Cloudfogger, just another case<\/h3>\n

Since (nearly) everybody has been lured into the cloud, also personal data are stored online. But there is no control, where private data are stored within the cloud. To protect private data, some people are encrypting them, before uploading them to the cloud. One popular tool available for cloud data encryption was Cloudfogger<\/a> \u2013 but the project has been cancelled. The successor is www.boxcryptor.com<\/a>. The Cloudfogger client was useable in Windows 10 RTM, but during the next feature upgrade (Windows as a service is greeting) users are facing problems.<\/p>\n

Upgrade to Windows 10 Anniversary Update fails with error 0x80070057<\/h3>\n

Error 0x80070057 has become a personal obsession to me, because I was facing this error within many MS Answers forum posts. Error diagnose for this error has been always a kind of \"searching a needle within a hay stack\". Error\u00a0 0x80070057 has been hit users during upgrade to Anniversary Update many times (but this error isn't restricted to Windows 10 Version 1607). I've discussed several root causes within my blog post Windows 10: Update error 0x80070057<\/a>.<\/p>\n

In many cases it ends with a clean install of Windows 10 using an install media (created with Media Creation Tool). My German blog post about error 0x80070057 received many hits and one blog reader left a comment<\/a>, claiming Cloudfogger as a show stopper. Also another user confirmed Cloudfogger and it's filter driver cbfltfs4.sys <\/em>as a root cause for error 0x80070057.<\/p>\n

The successor Boxcryptor doesn't have this problem \u2013 a developer left a comment, that Boxcryptor's filter driver is compatible with Windows 10.<\/p><\/blockquote>\n

Creating a Recovery drive drops error 0x80070057<\/h3>\n

During writing the German blog post about error 0x80070057, I found this this Microsoft Answers forum thread<\/a>. User pcguru3482<\/em> reported in November 2015, that encryption tool Cloudfogger was responsible for this error.<\/p>\n

The DISM WIM mount error delivers some hints<\/h3>\n

After reading some forum posts, the puzzle completed, as I came across this sysnative.com forum post<\/a>. A user has posted his log file, found at C:\\$WINDOWS.~BT\\Sources\\Panther \\setuperr<\/em>:<\/p>\n

2016-08-03 13:38:34, Error                 SP     SPMountWIMCallback: Error mounting\/unmouting C:\\$WINDOWS.~BT\\Sources\\SafeOS\\SafeOS.Mount\\windows\\winsxs\\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ecb\\CbsMsg.dll. GLE [87][gle=0x00000057]2016-08-03 13:38:44, Error                 SP     CMountWIM::DoExecute: Failed to mount WIM file C:\\$WINDOWS.~BT\\Sources\\SafeOS\\winre.wim. Error 0x80070057[gle=0x00000057]\r\n2016-08-03 13:38:44, 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]\r\n2016-08-03 13:38:44, Error                 MOUPG  MoSetupPlatform: ExecuteCurrentOperations reported failure!\r\n2016-08-03 13:38:44, Error                 MOUPG  MoSetupPlatform: Using action error code: [0x80070057]\r\n2016-08-03 13:38:44, Error                 MOUPG  CDlpActionImageDeploy::ExecuteRoutine(403): Result = 0x80070057\r\n2016-08-03 13:38:44, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result = 0x80070057\r\n2016-08-03 13:38:44, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0x80070057\r\n2016-08-03 13:38:45, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0x80070057\r\n2016-08-03 13:38:45, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0x80070057\r\n2016-08-03 13:38:45, Error                 MOUPG  CSetupManager::ExecuteTask(2067): Result = 0x80070057\r\n2016-08-03 13:38:45, Error                 MOUPG  CSetupManager::ExecuteTask(2030): Result = 0x80070057\r\n2016-08-03 13:38:45, Error                 MOUPG  CSetupManager::ExecuteInstallMode(815): Result = 0x80070057\r\n2016-08-03 13:38:45, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(391): Result = 0x80070057\r\n2016-08-03 13:38:47, Error                 MOUPG  CSetupManager::Execute(236): Result = 0x80070057\r\n2016-08-03 13:38:47, Error                 MOUPG  CSetupHost::Execute(372): Result = 0x80070057<\/pre>\n
Installing Windows 10 Anniversary upgrade failed, because the WIM file containing the install image could not be mounted. Also within this superuser.com post<\/a> somebody complained, that upgrading from Windows 8.1 to Windows 10 Pro stalls at 23%. Analyzing setuperr.log<\/em> shows that mounting the WIM file failed with error 0x80070057.<\/p>\n
\"Process<\/p>\n
The user, hit by this error, fired up Sysinternals Process Monitor<\/a> and monitored the WIM mount process. The stack dump (see screenshot above) shows, that filter driver cbfltfs4.sys<\/em> is involved. With this knowledge it's easy to check a system for third party filter drivers as a possible root cause for install errors.<\/p>\n
\"Filtertreiberkette\"<\/p>\n
Open an administrative command prompt window (see Windows 10: Open command prompt window as administrator<\/a>) and enter the command fltmc filters<\/em>. This enlists all filter drivers installed within the system (the above screenshot enlists all filter drivers installed on my Windows 7 machine). Within the forum post mentioned above, the following filter drivers are enlisted:<\/p>\n
C:\\Windows\\system32>fltmc filters\r\n\r\n\r\nFilter Name                     Num Instances    Altitude    Frame\r\n------------------------------  -------------  ------------  -----\r\ncbfltfs4                                        429998.99   <Legacy>\r\neamonm                                  6       328700         0\r\nstorqosflt                              0       244000         0\r\nWIMMount                                3       180700         0\r\nFileCrypt                               0       141100         0\r\nluafv                                   1       135000         0\r\nnpsvctrig                               1        46000         0\r\nFileInfo                                6        45000         0\r\nWof                                     4        40700         0<\/pre>\n
Filter driver cbfltfs4 <\/em>is on this list \u2013 searching the Internet reveals, that this driver belongs to CloudFogger. FileCrypt <\/em>is the \u201eWindows sandboxing and encryption filter\" from Windows 10 (see<\/a>).<\/p>\n
I outlined the background information within this blog post. Maybe it helps to detect the root cause, if you are facing error 0x80070057 in future.<\/p>\n
Similar articles:
\n<\/strong>Win10 Wiki<\/a>
\nWindows 10: Open command prompt window as administrator
\n<\/a>Trick: How to upgrade to Windows 10 using a clean install
\n<\/a>Microsoft Windows and Office ISO download tool<\/a><\/p>\n
How to decode Windows errors?
\n<\/a>Windows 10: Analyze upgrade errors
\n<\/a>Windows: How to decode update 0x8024\u2026. errors<\/a><\/p>\n
Windows 10: Error 0x800704CF
\n<\/a>Windows 10: Upgrade error 80240020
\n<\/a>Windows 10: Upgrade error 0x80200013
\n<\/a>Windows 10: Upgrade error 0x80070570-0x2000C<\/a>
\nWindows 10: Upgrade error 0x8007002C-0x4000D
\n<\/a>Windows 10: Upgrade error 0xC1900101 \u2013 0x20003<\/a>
\n<\/a>Windows 10: Upgrade error 0xC1900101 \u2013 0x20004
\n<\/a>Windows 10: Upgrade error 0xC1900101-0x2000A
\n<\/a>Windows 10: Upgrade error 0xC1900101-0\u00d720017\/0\u00d730017
\n<\/a>Windows 10: Upgrade error 0xC1900101-0x2000C
\n<\/a>Windows 10 Anniversary Update: Upgrade error 0xA0000400
\n<\/a>Windows 10: Update error 0x80070057
\n<\/a>Windows 10: How to fix update error 0x80080008<\/a>
\nWindows 10: System restore fails with error 0x81000203<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
[German]Some users are receiving error 0x80070057 during distinct Windows 10 operations (backup, system restore, upgrades). Recently I stumbled upon Cloudfogger as a root cause for this error code. Here are a background information about this case.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63,463,22,2],"tags":[635,76],"class_list":["post-2114","post","type-post","status-publish","format-standard","hentry","category-cloud","category-issue","category-update","category-windows","tag-error-0x80070057","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=2114"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2114\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=2114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=2114"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=2114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}