1511 To 1607 Enterprise Feature Upgrade Failing

1511 to 1607 Enterprise feature upgrade failing
1/12/16 18'33
United States (English)
Search TechNet with Bing
Home
Library
Wiki
Learn
Ask a question
Gallery
Downloads
Search related threads
Support
Forums
Sign in
Blogs
Search forum questions
Quick access
Asked by:
160
1511 to 1607 Enterprise feature upgrade

failing
Points
Top 10%
Windows 10 IT Pro > Windows 10 Installation, Setup, and Deployment
gemidriver
Joined Nov 2008
gemidriver's thr
6
Question
Show activity
https://social.technet.microsoft.com/Forums/en-US/d2afda41-7f28-to-1607-enterprise-feature-upgrade-failing?forum=win10itprosetup
Pgina 1 de 32
1/12/16 18'33
We have 20+ machines running 1511 windows 10 in our enterprise. we are now trying to
upgrade to the anniversary update 1607 via WSUS server
3
Sign in
to vote
Failing to install on multiple machines

Feature update to Windows 10 Enterprise, version 1607, en-us - Error 0xc1800118
I patched the WSUS server, approved the feature upgrade for the PCs
they seem to download the file, it goes into softwaredistribution folder, then the
$Windows.~BT folder becomes 2.5gb in size
it tries to install, I can see the windows 10 install exe in the task manager
then fails..
setupact.log
2016-08-18 10:04:18, Error
SP
CSetupPlatform::ResurrectNewSystem: Cannot
resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: The
system cannot find the file specified. [0x00000002] __cdecl
UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum
UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]
2016-08-18 10:04:18, Warning
MOUPG ImageExit: Unable to resurrect NewSystem
object. hr=0x80070002
setuperr.log
2016-08-18 10:04:15, Error
MOUPG RecoverCrypto: File is encrypted, but no key
was provided.
2016-08-18 10:04:15, Error
MOUPG CDlpActionRecoverCrypto::DoCrypto(1713):
Result = 0xC1800118
2016-08-18 10:04:15, Error
MOUPG
CDlpActionRecoverCrypto::ExecuteRoutine(2465): Result = 0xC1800118
2016-08-18 10:04:15, Error
MOUPG CDlpActionImpl<class CDlpErrorImpl<class
CDlpObjectInternalImpl<class CUnknownImpl<class IDlpAction> > > >::Execute(441): Result
= 0xC1800118
2016-08-18 10:04:15, Error
MOUPG CDlpTask::ExecuteAction(3243): Result =
0xC1800118
2016-08-18 10:04:16, Error
MOUPG CDlpTask::ExecuteActions(3397): Result =
0xC1800118
2016-08-18 10:04:16, Error
MOUPG CDlpTask::Execute(1631): Result =
0xC1800118
2016-08-18 10:04:16, Error
MOUPG CSetupManager::ExecuteTask(2067): Result =
0xC1800118
2016-08-18 10:04:16, Error
MOUPG CSetupManager::ExecuteTask(2030): Result =
0xC1800118
2016-08-18 10:04:16, Error
MOUPG CSetupManager::ExecuteInstallMode(690):
Result = 0xC1800118
2016-08-18 10:04:16, Error
MOUPG
CSetupManager::ExecuteDownlevelMode(391): Result = 0xC1800118
2016-08-18 10:04:18, Error
SP
resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: The
system cannot find the file specified. [0x00000002] __cdecl
Edited by
gemidriver
Thursday, August 18, 2016 12:16 AM

Reply | Quote
gemidriver Tomago Aluminium Company
160 Points
Pgina 2 de 32
1/12/16 18'33
All replies
We are experiencing a similar issue trying to deploy 1607 using Configuration Manager
1606 (5.0.8412.1000). We have a simple single server SCCM infrastructure.
2
Sign in
to vote
The required KB3159706 has been installed on the server, and the additional steps in "More
information" at the bottom of that KB article have also been carried out.
We see a very similar error -- this is from $Windows.~BT\Sources\Panther\setupact.log:
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
08:39:02,
08:39:02,
08:39:02,
08:39:02,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:03,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:04,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:05,
08:39:06,
08:39:06,
08:39:06,
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Warning
Info
Info
Error
Error
Error
Warning
Warning
Error
Info
Error
Warning
Warning
Error
Info
Info
Warning
Warning
Error
Warning
Info
Error
Error
Error
Error
Info
Info
Info
Info
Info
Info
MOUPG SetupManager::DetermineSetupPhase: CurrentS

MOUPG Setup phase change: [SetupPhaseUnknown
MOUPG SetupManager::OpenOrCreateTask: Creating
MOUPG CreateTask: Name = [Unpack], WorkingPath
MOUPG RecoverCrypto: Entering Prepare Method
MOUPG RecoverCrypto: Leaving Prepare Method
MOUPG UpgLayout: Entering Prepare Method
MOUPG UpgLayout: Leaving Prepare Method
MOUPG RecoverCrypto: Initializing Wim Source Path
MOUPG RecoverCrypto: Initializing Wim Target Path
MOUPG RecoverCrypto: Initializing Remote Source
MOUPG RecoverCrypto: Initializing Crypto Key [No
MOUPG RecoverCrypto: Initializing Size: [0x0]
MOUPG RecoverCrypto: Initializing Flags: [0x4]
MOUPG RecoverCrypto: Initializing Hash Type: [0
MOUPG RecoverCrypto: Initializing Hash Value: [NULL
MOUPG RecoverCrypto: Initializing DeleteSource
MOUPG SetupNotify::CleanupCachedFile - Cleaning
MOUPG SetupManager: InstallAttempts = [6]
MOUPG DlpTask: Entering Execute Method
MOUPG DlpTask: Transport not set. Skipping download
MOUPG DlpTask: Executing Actions...
MOUPG Action execution thread timeout period: [1000
MOUPG ProgressHandlerAction: Sending initial progress
MOUPG CSetupDiagnostics::ReportData - Not reporti
MOUPG RecoverCrypto: Entering Execute Method
MOUPG DlpTask: Resetting action [0] progress start time
MOUPG RecoverCrypto: File is encrypted, but no key wa
MOUPG CDlpActionRecoverCrypto::DoCrypto(1713
MOUPG CDlpActionRecoverCrypto::ExecuteRoutine
MOUPG RecoverCrypto: Leaving Execute Method
MOUPG CDlpTask::ExecuteActions(3397): Result
MOUPG Waiting for actions thread to exit.
MOUPG Actions thread has exited.
MOUPG CDlpTask::Execute(1631): Result = 0xC180011
MOUPG DlpTask: Leaving Execute Method
MOUPG CSetupManager::ExecuteTask(2067): Result
MOUPG CSetupManager::ExecuteInstallMode(690
MOUPG CSetupManager::ExecuteDownlevelMode
MOUPG Setup phase change: [SetupPhaseUnpack]
MOUPG SetupManager::OpenOrCreateTask: Found
MOUPG SetupManager::OpenOrCreateTask: Deleting
MOUPG SetupManager::OpenOrCreateTask: Deleted
MOUPG SetupManager::OpenOrCreateTask: Creating
MOUPG CreateTask: Name = [Exit], WorkingPath =
Pgina 3 de 32
1/12/16 18'33
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
2016-08-18
08:39:06,
08:39:06,
08:39:06,
08:39:06,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
08:39:07,
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Warning
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Warning
Info
Info
Info
Info
Warning
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Error
Warning
MOUPG Finalize: Entering Prepare Method

MOUPG Finalize: Leaving Prepare Method
MOUPG DlpTask: Entering Execute Method
MOUPG DlpTask: Transport not set. Skipping download
MOUPG DlpTask: Executing Actions...
MOUPG Action execution thread timeout period: [1000
MOUPG ImageExit: Initializing SetupResult: [0xc180011
MOUPG ImageExit: Initializing Extended: [0x30002
MOUPG ImageExit: Initializing Scenario: [5]
MOUPG ImageExit: Initializing Mode:
[2]
MOUPG ImageExit: Initializing Target:
[C]
MOUPG ImageExit: Initializing SQM:
[TRUE]
MOUPG ImageExit: Initializing PostReboot: [FALSE
MOUPG ProgressHandlerAction: Sending initial progress
MOUPG Finalize: Entering Execute Method
MOUPG MoSetupPlatform: Loading Setup Platform
MOUPG MoSetupPlatform: Determine if the expected ve
MOUPG MoSetupPlatform: Platform and Setup binaries m
MOUPG MoSetupPlatform: Attempting resurrect of
SPVerifyFootprint: Starting verification of footprint s
SPVerifyFootprint: The requested footprint is presen
SPGenerateCopyListFromConfigFile: Didn't find file
SPVerifyFootprint: Starting verification of footprint sec
SPVerifyFootprint: The requested footprint is present
SPGenerateCopyListFromConfigFile: Didn't find file list
SPVerifyFootprint: Starting verification of footprint s
SPVerifyFootprint: Could not find footprint file C
SPVerifyFootprint: The requested footprint is not
SPGetFootprintCapabilities: Footprint [Footprint
SPGenerateCopyListFromConfigFile: Didn't find file
SPVerifyFootprint: Starting verification of footprint sec
SPVerifyFootprint: Could not find footprint file C:\$WIN
SPVerifyFootprint: The requested footprint is not prese
SPGetFootprintCapabilities: Footprint [Footprint.Mig
SP
CSetupPlatform::Initialize: Setup log starts:
There is already a running setup user mode etw sessio
VDS available
MOUPG MoSetupPlatform: Setup Platform object resurrecte
MOUPG MoSetupPlatform: Enable diagnosis mode
Key CollectTrace is not available.
MOUPG MoSetupPlatform: Persisting telemetry data
MOUPG MoSetupPlatform: Not persisting telemetry data
MOUPG MoSetupPlatform: Resurrecting NewSystem object
SP
Attempting to resurrect a new system from C:\$Wind
SP
CSetupPlatform::ResurrectNewSystem: Cannot resurr
MOUPG ImageExit: Unable to resurrect NewSystem obje
Is there some way to validate the proper configuration of the KB3159706 post-install steps
that we can do?

Reply | Quote
TestValleySchool
30 Points
Pgina 4 de 32
1/12/16 18'33
I have same issue

I have the following:
2
Sign in
to vote
-windows 2012 wsus 6.2

-wsus patched and approved feature upgrade 1607
-clients detect the feature upgrade and start downloading then it fail with
Feature update to Windows 10 Enterprise, version 1607, en-us - Error 0x8000fff

Reply | Quote
HussainMahfood
20 Points
HussainMahfood
20 Points
Also I added the mime type ESD to the IIS to support it

Reply | Quote
Sign in
to vote
Same problem here, but randomly. 1/3 of machines cannot update.

Reply | Quote
yannara Fujitsu (Partner)
Sign in
to vote
2,950 Points
Same error 0xc1800118 here. None of founded tips and patches resolved problem, yet.
Thursday, August 18, 2016 12:51 PM
Reply | Quote
Sign in
to vote
CSAD Florenc
60 Points
I did wider test, and my results shows, that after 3-4 retries it kicks off fine and reboots
into the installation process itself. I use Confmgr cb v1606.
1
Sign in
to vote

Reply | Quote
2,950 Points
Also having the same error.

The software change returned error code 0xC1800118(-1048575720).
1
Sign in
to vote

Reply | Quote
semtex41
5 Points
Pgina 5 de 32
1/12/16 18'33
1
Sign in
to vote
Sorry, can`t confirm that. Many retries on more computers with no success.
Friday, August 19, 2016 6:01 AM
Reply | Quote
CSAD Florenc
60 Points
1
Sign in
to vote
Would you be able to provide a snippet of the setupact.log from when it works successfully?
We have not yet had any success after multiple retries in our environment and I'm curious
as to any differences in the logs.
Reply | Quote
TestValleySchool
30 Points
Solution:
http://moonlightsoft.blogspot.pt/2016/08/error-0x80244019-occurred-while.html
3
Sign in
to vote
Worked like a charm (i used google translate)

You need to add extension .esd with MIME TYPE "application/vnd.ms-cab-compressed" on
MIME Types on CONTENT of WSUS Administration on IIS

Reply | Quote
RDDuarte (Partner)
15 Points
For me, this is not the solution.

The software center is able to dowload the update with this MIME type also without.
The error appears when the client tries to install the update.
Sign in
to vote

Reply | Quote
Ps1_2012
10 Points
Also having the same error.

The software change returned error code 0xC1800118(-1048575720).
1
Sign in
to vote

Reply | Quote
surfer13
5 Points
Pgina 6 de 32
1/12/16 18'33
For me, this is not the solution.

The software center is able to dowload the update with this MIME type also without.
1
Sign in
to vote
The error appears when the client tries to install the update.
Yes, I can confirm this! The error is about upgrade process itself inside Win10 OS, not in CM
process.
Friday, August 19, 2016 1:19 PM
Reply | Quote
2
Sign in
to vote
2,950 Points
2016-08-19 16:51:42, Error

SP
resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: Het
systeem kan het opgegeven bestand niet vinden. [0x00000002] __cdecl
2016-08-19 16:53:11, Error
MOUPG RecoverCrypto: File is encrypted, but no
key was provided.
2016-08-19 16:53:11, Error
Result = 0xC1800118
so i see 2 problems
the system cannot find the file NewSystem.dat
file is encrypted, but no key was provided
*edit: disabling Defender and trying again changed the error to 0xC1900107 and empied
the Windows.~BT map so no error logs at the moment
*edit2: And trying again, Defender still disabled, I end up getting error 0xC1800118 again
Edited by
RedDevil BE

Reply | Quote
RedDevil BE
80 Points
Hello,
testing also Windows 10 1607 upgrade with SCCM 1606.
1
Sign in
to vote
Most upgrades success but got same error (0xC1800118) with few test PC. Failed PC had
older SCCM Client, version 5.0.8325.1000 and 5.0.8355.1306. SCCM client never upgraded
automatically because of switched off long time. Anyway I run SCCM client upgrade
scheduled task manually and after that Windows 10 1607 upgrade success.
KR. Jyrki
Proposed as answer by
RedDevil BE
Saturday, August 20, 2016 9:39 AM

Reply | Quote
jyrppa
10 Points
Pgina 7 de 32
1/12/16 18'33
Just as jyrppa noticed, the client version does matter.
2
Sign in
to vote
On my test machine the SCCM Client Version was still 5.00.8355.1306 and the installation
failed with Error 0xc1800118
It turns out the option to enable the automatic upgrade of the clients, in the hierarchy
settings of the site, was not enabled.
After enabling it on the server, then -on the test machine- triggering the machine
evaluation policy in the configuration manager and (manually) executing the Upgrade Task
that appeared in the Task Planner, the client was updated to 5.00.8412.1000.
little side note: I had to reboot the machine before I saw the task, propably because it
came from hybernation
In Software Center I tried the upgrade again and it succeeded.
So all together, what I had to do:
Make sure the server is updated. Check if KB3159706 is installed and preform the
manual task(s)
Upgrade the Configuration Manager Console to version 1606
Upgrade the client machines to 5.00.8412.1000 and/or check if the automatic
upgrade is enabled.
Then you'll have no problems downloading the Feature update to Windows 10 Enterprise,
version 1607, distributing and installing it
*edit*
If you are having download problems:
Error 0x80244019:
As RDDuarte suggested, you can follow the steps in this post.
However I did not expericence it myself, a colleague told me it fixed his download problem.
Error 'You have no permission to download...':
Make sure you have all the rights on the folder where you want to download the update to
Edited by
RedDevil BE
joshhmorg
Tuesday, September 06, 2016 5:07 PM

Reply | Quote
RedDevil BE
80 Points
Verd odd as I have all this in place and still fails with the error
Saturday, August 20, 2016 12:58 PM
1
Sign in
to vote
Reply | Quote
Pitmand
5 Points
Pgina 8 de 32
1/12/16 18'33
Hi,
I've got the same behavior like jyrppa.
1
Sign in
to vote
My environment:
- SCCM CB Version 1511 (Server 2012)
- separat WSUS (Server 2012)
- Download of 1607-Update worked with the first try (then my client got 0xC1800118)
What I've done:
- installed KB3159706 on WSUS and SCCM
- added *.esd support to the IIS of the WSUS and also to the SCCM-IIS -> no change
- deleted the downloaded 1607-upadate und redownloaded it with the *.esd-settings ->
no change
- upgraded my SCCM to CB 1606 -> no change
- upgraded the SCCM-Client version manually by triggering the Windows-Task to version
5.00.8412.1007 (automatic upgrade for all clients enabled) and deleted the cache of the
client -> update worked like a charme
So the client-version definitely plays a role
Edited by
soch234
Monday, August 22, 2016 9:48 AM

Reply | Quote
soch234 (Partner)
15 Points
Thanks soch234, clearing cache fixed my TestPCs reporting 'Compliant' and is now
downloading updates fine. Tho still fails after download and Install starts. Tested all your
steps with same result, no change.
1
Sign in
to vote
Ive also tried adding the ".esd" "application/octet-stream", no change.

2016-08-22 10:51:25, Error
key was provided.
SCCM client: 5.00.8412.1007
Edited by
danbro92

Reply | Quote
danbro92
15 Points
Pgina 9 de 32
1/12/16 18'33
1
Sign in
to vote
I forgot to mention, that I've installed KB3159706 on both servers (WSUS and SCCM) as
described in this
article: https://blogs.technet.microsoft.com/enterprisemobility/2016/08/05/update-yourconfigmgr-1606-sup-servers-to-deploy-the-windows-10-anniversary-update/
Reply | Quote
soch234 (Partner)
15 Points
danbro92
15 Points
I got KB3159706 aswell with steps completed. Not using SSL.

Reply | Quote
Sign in
to vote
1
Sign in
to vote
2016-08-19 16:51:42, Error

SP
CSetupPlatform::ResurrectNewSystem:
Cannot resurrect new system.: Win32Exception: \\?
\C:\$Windows.~BT\Sources\NewSystem.dat: Het systeem kan het opgegeven bestand
niet vinden. [0x00000002] __cdecl UnBCL::FileStream::FileStream(const class
UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum
UnBCL::FileShare,unsigned long)[gle=0x00000002]
2016-08-19 16:53:11, Error
MOUPG RecoverCrypto: File is encrypted, but
no key was provided.
2016-08-19 16:53:11, Error
MOUPG
CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118
so i see 2 problems
the system cannot find the file NewSystem.dat
file is encrypted, but no key was provided
*edit: disabling Defender and trying again changed the error to 0xC1900107 and
empied the Windows.~BT map so no error logs at the moment
*edit2: And trying again, Defender still disabled, I end up getting error 0xC1800118
again
Same problem here, after some retries it created a $GetCurrent folder (next to the
$WINDOWS.~BT on C:), after deleting these its back to 0xC1800118. hmm...
Edit: Appears the 0xC1900107 error is occuring when browsing the log files in the
$WINDOWS.~BT folder at the same time as starting a retry, The setupprocess cant clear the
folder I guess(?)
Edited by
danbro92

Reply | Quote
danbro92
https://social.technet.microsoft.com/Forums/en-US/d2afda41-7f28-o-1607-enterprise-feature-upgrade-failing?forum=win10itprosetup
15 Points
Pgina 10 de 32
1/12/16 18'33
Hello,
testing also Windows 10 1607 upgrade with SCCM 1606.
Most upgrades success but got same error (0xC1800118) with few test PC. Failed PC
had older SCCM Client, version 5.0.8325.1000 and 5.0.8355.1306. SCCM client never
upgraded automatically because of switched off long time. Anyway I run SCCM
client upgrade scheduled task manually and after that Windows 10 1607 upgrade
success.
Sign in
to vote
KR. Jyrki
Yes, I can confirm this! Updating CM client to 5.00.8412.1000 version was my last resolve.
Tuesday, August 23, 2016 4:53 AM
Reply | Quote
2,950 Points
We continue to see the errors with no change in behaviour, even with the CM client on
5.00.8412.1007.
2
Sign in
to vote

Reply | Quote
TestValleySchool
30 Points
But what shall we do if we don't use SCCM as Update Source? We use WSUS.
Reply | Quote
Alexey Litvinov
Sign in
to vote
100 Points
We do not use SCCM also and We use WSUS only

What shall we do ?????
1
Sign in
to vote
Tuesday, August 23, 2016 1:20 PM

Reply | Quote
HussainMahfood
20 Points
I have the same problem. WSUS on Windows Server 2012 (not R2). We have 190 Windows 10
clients!
0
Sign in
to vote
Server 2012
-
Windows server is up to date

installed KB3159706 - manual config steps was done
added *.esd - application/octet-stream support to the IIS of the WSUS
for sure I try delete and the redownload 1607 updates, according to KB3095113
Client Windows 10 1511 bulid 10586.544

- detect new Windows Anniversary Update 1607
- update create C:\WINDOWS.BT but failed with error 0xc1800118
c:\$WINDOWS.~BT\Sources\Panther\setuperr.log:
2016-08-24 07:49:51, Error
[SetupHost.Exe] IOCTL_STORAGE_QUERY_PROPERTY
Pgina 11 de 32
1/12/16 18'33
2016-08-24
2016-08-24
2016-08-24
2016-08-24
2016-08-24
07:49:51,
07:49:57,
07:51:19,
07:51:19,
07:51:19,
Error
Error
Error
Error
Error
[SetupHost.Exe] IOCTL_STORAGE_QUERY_PROPERTY
SP
MOUPG RecoverCrypto: File is encrypted, but no key wa
MOUPG CDlpActionRecoverCrypto::DoCrypto(1713
MOUPG CDlpActionRecoverCrypto::ExecuteRoutine
WindowsUpdate.log:
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
2016.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
08.
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
24
07:51:14.8174487
07:51:14.8233793
07:51:14.8233883
07:51:14.8233887
07:51:14.8233932
07:51:15.6378869
07:51:15.6503269
07:51:15.6503881
07:51:15.6503912
07:51:15.6503921
07:51:15.6842552
07:51:15.6843123
07:51:15.7119190
07:51:15.7127107
07:51:15.7127111
07:51:15.7174132
07:51:15.7179550
07:51:15.7179563
07:51:15.7179572
07:51:15.7207489
07:51:16.1393673
07:51:18.8141634
07:51:35.0995312
07:51:35.1000997
07:51:35.1001015
07:51:35.1009672
07:51:35.1013496
07:51:35.1013519
07:51:35.1031971
07:51:35.1257224
07:51:35.1445514
07:51:35.1445817
07:51:35.1445835
07:51:35.1446482
07:51:35.1446486
07:51:35.1446495
07:51:35.1446513
07:51:35.1490375
1028
1028
1028
1028
1028
1028
1028
1028
1028
1028
1028
1028
1028
6872
6872
6872
6872
6872
6872
6872
6872
6872
6872
6872
6872
6872
6872
6872
1028
1028
1028
1028
1028
1028
1028
1028
1028
1028
9656 Agent
Updates to install = 1
9656 Agent
Title = Aktualizace funkc?? Window
9656 Agent
UpdateId = 803BEA9D-CD999656 Agent
Bundles 1 updates:
9656 Agent
8A4A5746-BDFA-4659-AD25
9656 Handler
Loaded state. m_dwState now: Setup
6256 Misc
Got WSUS Client/Server URL: http
6256 ProtocolTalker OK to reuse existing configuration
6256 ProtocolTalker Existing cookie is valid, just
6256 ProtocolTalker PTInfo: Server requested registrati
6256 Misc
Got WSUS Reporting URL: http://wsus.
6256 WebServices
Auto proxy settings for this web se
9656 DownloadManager Preparing update for install
3192 Handler
* START * Windows Setup Install
3192 Handler
Updates to install = 1
3192 Handler
Loaded state. m_dwState now: Setup
3192 Handler
Starting Windows Setup with comma
3192 Handler
HandlerSecsInADay = 86400.
3192 Handler
Registering WinSetup COM server
3192 Handler
Successfully registered WinSetup
12992 Handler
Requested file 14393.0.160715
12992 Handler
Deleting setup file '14393.0.160715
3192 Handler
Installer completed. Process return
3192 Handler
Handler: Setup360 returned unknow
3192 Handler
State changed. was: Setup360_Comp
3192 Handler
Saved state. m_dwState: <invalid>
3192 Handler
Exit code = 0x80248008
3192 Handler
* END * Windows Setup Install
9656 Handler
Loaded state. m_dwState now: <inval
9656 Agent
LogHistory called. idUpdate={803BEA
9656 Agent
Installing updates CallerId = UpdateO
16160 ComApi
Install ClientId = UpdateOrchestra
16160 ComApi
Install call complete (succeeded
16160 ComApi
Reboot required = False
16160 ComApi
Exit code = 0x00000000; Call
16160 ComApi
* END * Install ClientId = UpdateO
16160 Agent
WU client calls back to install call
15784 ComApi
ISusInternal:: DisconnectCall
Wednesday, August 24, 2016 6:58 AM

Reply | Quote
miki17
0 Points
Pgina 12 de 32
1/12/16 18'33
We are also seeing error 0xC1800118.
0
Sign in
to vote
KB3159706 installed and manual steps completed. We are running ConfigMgr CB 1606 and
the client reporting 0xC1800118 has the latest ConfigMgr client (5.00.8412.1007).
Our WSUS is also running on Server 2012 without R2, could the issue be related to this?
Has anyone been able to get this working with a WSUS running on Server 2012? Also, is
anyone having this issue with a WSUS running on Server 2012 R2?
Edited by
CalleW

Reply | Quote
CalleW
65 Points
Well there you said it CalleW, it could very much be a Server 2012 (Not R2) problem. Im
running without R2 aswell.
0
Sign in
to vote

Reply | Quote
danbro92
15 Points
CalleW, we are running our WSUS also on Server 2012 without R2, our SCCM also runns on a
different Server 2012 without R2. Installing the Win10-1607-Upgrade was succsessful on
one client
0
Sign in
to vote

Reply | Quote
soch234 (Partner)
15 Points
Since I'm not experiencing any more errors (SCCM+WSUS), I can only suggest what I would
do if I' was able to see and download the update but expercience this error non the less,
with only WSUS.
1
Sign in
to vote
On the client computer:

->
->
->
->
->
make sure the client is 100% up-to-date with the current build
disable the Windows Update service
delete the C:\Windows\SoftwareDistribution folder
enable the Windows Update service
search for the update again
-> optionally: disable and anti-virus
Edited by
RedDevil BE

Reply | Quote
RedDevil BE
80 Points
Pgina 13 de 32
1/12/16 18'33
Has anyone been able to get this working with a WSUS running on Server 2012? Also, is
anyone having this issue with a WSUS running on Server 2012 R2?
0
Sign in
to vote
I'm running 2012 R2. Had an error, 1607 wouldn't even download, just failed immediately.
Did the MIME addition, clients now download 1607, but when going to install they get
0x08000ffff. Not sure why updates started becoming such a headache recently. Blew out
the update on my WSUS server and re-downloaded it thinking maybe it was corrupt. Didn't
fix the problem.
Edited by
Wednesday, August 24, 2016 2:46 PM
AngelOfProgress

Reply | Quote
AngelOfProgress
0 Points
so can you confirm that you've applied the hotfix plus manual changes, and that you
removed (deleted) the 1607 updates in your WSUS console, then resynced your SUP and still
had the same problem ?
0
Sign in
to vote
Step by Step Configuration Manager Guides > https://www.windowsnoob.com/forums/topic/13288-step-by-step-guides-system-center-configurationmanager-current-branch/

Reply | Quote
Niall C. Brady A Global Company (MCC, Partner, MVP)
19,665 Points
how can i delete those 1607 updates?

just deny them?
0
Sign in
to vote
Paz2016
Unproposed as answer by
Paz2016

Reply | Quote
shoclate
0 Points
Pgina 14 de 32
1/12/16 18'33
Hi,
i deleted the files by those steps:
2
Sign in
to vote
1. Uncheck "Windows 10" and "Upgrades" under "Products and Classifications"

2. Decline all 1607 Updates
3.$s = Get-WsusServer
$s.SearchUpdates(version 1607) | foreach { $s.DeleteUpdate($_.Id.UpdateId) }
4. Start the "Server Cleanup Wizard" and delete "Unneeded Files"
5. Tick "Windows 10" and "Upgrades" under "Products and Classifications"
6. Resync
Edited by
Paz2016

Reply | Quote
0
Sign in
to vote
Paz2016
25 Points
I can confirm that i've applied the hotfix and done the manual changes. After that I also
declined and deleted the 1607 upgrade in my WSUS via powershell. I then resynced and
approved the update again. But my test computers still get error 0xc1800118 as soon as
they try to install the update. I've used our helpdesks computers as guinea pigs but they all
get the same problem (all running Windows 10 version 1511). And i've also tried on several
freshly installed virtual machines but alas...
Reply | Quote
Andreas_N
0 Points
Hi Guys,
we had same issue in various environments and the issue is now resolved.
0
Sign in
to vote
If you are receiving File is encrypted, but no key was provided,

CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118, then it is time to reinstall the SUP
Installing KB3159706 and post installation manual steps will not resolve the problem.
Remove the SUP and re-install it. This will fix the error 0xC1800118.
I have tested on 2 different environments and after the SUP re-install we can deploy feature
upgrade 1607 successfully.
For further information, please refer to this article;
http://venusingireddy.blogspot.com.au/2016/08/recovercrypto-file-is-encrypted-butno.html
Cheers,
Vneu
Saturday, August 27, 2016 2:31 PM

Reply | Quote
Venu Singireddy
1,155 Points
Pgina 15 de 32
1/12/16 18'33
Hi Guys,
2
Sign in
to vote

CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118, then it is time to
re-install the SUP
I have tested on 2 different environments and after the SUP re-install we can deploy
feature upgrade 1607 successfully.
Cheers,
Vneu
Our WSUS enviroment is pretty big and thoroughly configured. I don`t want to reinstall it
now (2 days of work). It is not solution for us. But for somebody it can by satisfying.
Reply | Quote
0
Sign in
to vote
CSAD Florenc
60 Points
so can you confirm that you've applied the hotfix plus manual changes, and that you
removed (deleted) the 1607 updates in your WSUS console, then resynced your SUP and
still had the same problem ?
Yup, confirmed. Done all that, same issues.
Monday, August 29, 2016 1:37 PM
Reply | Quote
AngelOfProgress
0 Points
same issue here too.
0
Sign in
to vote
Hotfix, manual steps, deleted the servicing plan, removed the package, updates still
received 0xC1800118 error. In our test SCCM 1606, re-installed SUP then it worked. First it
broke WSUS by crashing MMC console as part of re-installation. Tried re-install second time
then it worked. We have started migrating the client to CB 1606, but not sure whether we
want to re-install SUP in the prod and put up with this all the troubles?? or do we have any
other better solution.
can please someone confirm if they fixed it any other ways?
Monday, August 29, 2016 7:38 PM

Reply | Quote
JaCkMl
0 Points
Pgina 16 de 32
1/12/16 18'33
and by resync you mean resync your SUP ? did these steps resolve the problem for you ?
Sign in
to vote

Reply | Quote
Niall C. Brady A Global Company (MCC, Partner, MVP)
19,665 Points
Hi Guys,
0
Sign in
to vote
CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118, then it is time to
re-install the SUP
I have tested on 2 different environments and after the SUP re-install we can deploy
feature upgrade 1607 successfully.
Cheers,
Vneu
Our WSUS enviroment is pretty big and thoroughly configured. I don`t want to reinstall
it now (2 days of work). It is not solution for us. But for somebody it can by satisfying.
Yeah I'm on the same boat... I don't feel like doing all of that...
Tuesday, August 30, 2016 9:47 PM
Reply | Quote
Nick Bitzan
5 Points
At the frist try I recive the error 0xC1800118.
0
Sign in
to vote
So for the second try I deleted the SoftwareDistribution folder. After a short Installation time
the installation finished
with "Installed". But winver displays still the old version. I also made several reboots, still
the old os version.
Does someone have any idea about this? At which logfile should I look at?

Reply | Quote
Ps1_2012
10 Points
Pgina 17 de 32
1/12/16 18'33
0
Sign in
to vote
I'm at this point as well. Needing to remove/add the SUP role. My question is, if I remove
the role...wait for it to complete....add the role back in and reconfigure with the same
settings: What else would need done afterwards? How does the removal/add of the SUP role
effect my existing software update groups, packages, approvals, ADR's etc.?
Reply | Quote
Andrew Westh
0 Points
Maybe this post helps to understand what may be going on.
0
Sign in
to vote
https://blogs.technet.microsoft.com/enterprisemobility/2016/08/05/update-yourconfigmgr-1606-sup-servers-to-deploy-the-windows-10-anniversary-update/
Looks like the way to manage encription keys changed on W10:
This update is necessary for WSUS to be able to natively decrypt the

encrypted Windows 10 Anniversary Update packages, and any
subsequent Windows 10 feature upgrades
I hope that this helps.
Raul Systems Support
Thursday, September 01, 2016 12:56 PM

Reply | Quote
0
Sign in
to vote
Raul de Microsoft CSS (MSFT)
0 Points
I have already done the steps Raul de has proposed and it still does not work. The problem
I have is with the installation of Windows 10 build 1607, not the decryption. I also notice
that updates like "Cumulative Update for Windows 10 Version 1607 for x64 based Systems
(KB3176938) will not download to client PC's on my network from my WSUS server if the
client has been upgraded to 1607 manually. The download on the client PC gets stuck at
0%. If I remove the client PC from my domain and get the update from Microsoft, it works
fine. I can then put the client back on my domain.
Edited by
IAGoldWing

Reply | Quote
IAGoldWing
5 Points
Pgina 18 de 32
1/12/16 18'33
At the frist try I recive the error 0xC1800118.
0
Sign in
to vote
So for the second try I deleted the SoftwareDistribution folder. After a short Installation
time the installation finished
with "Installed". But winver displays still the old version. I also made several reboots,
still the old os version.
Does someone have any idea about this? At which logfile should I look at?
If shows 'installed' and/or 'compliant', clear the cache and it will retry. If a real Success,
winver will show 1607.
see pic below
Edited by
danbro92

Reply | Quote
danbro92
15 Points
So I think maybe the problem that I have was I had upgrades selected in WSUS prior to
installing patch KB3159706, so when WSUS synced it downloaded all of the content prior to
the hotfix installation.
0
Sign in
to vote
After Installing KB3159706, I resynced WSUS, and then SCCM SUP. Deployments are
downloading fine, however Im getting the famous
RecoverCrypto: File is encrypted, but no key was provided. In
Pgina 19 de 32
1/12/16 18'33
c:\$WINDOWS.~BT\Sources\Panther\setuperr.log:
I have deleted all of my Windows 10 deployment rings service plans, updates..ect
In WSUS I declined 1607 then I removed update, upgrades, update rollups classification just
to be safe and ran WSUS cleanup wizard, along with the PowerShell commands to delete the
updates (just in case)
I opened up SUP, and removed upgrades classification as well.
Resynced both SUP and WSUS with these classifications off.
Restarted
Re-enabled the classification on WSUS, resynced:
1607 came back in the list, however it seems like It didnt download anything new.
{I think this is the problem}
Re-enabled the classification on SUP, resynced:
1607 came back on the list
Created new Windows 10 Service Ring
Same Problems.
It seems to me that the package is still downloaded via WSUS without the decrypt key, and I
keep on deploying out that version via WSUS\SCCM because when I delete it and reapprove
it its not downloading anything
I right clicked and looked at the update file information and I get this. (theres more info
then this, but this is most likely my problem)
File Name: 14393.0.160715-1616.rs1_release_CLIENTENTERPRISE_VOL_x64fre_enus.esd

Location:
MYWSUSSERVER/Content/49/47ABC117B9D3DE907B4C72F5D30E2C377BCCD749.esd
File Type: Unspecified
File Size: 2663509020 bytes
Modified: 7/16/2016 8:18
Language: English
My question to MS: Can you manually delete these esds? without breaking WSUS?
Im thinking of repeating my process and this time delete these files and hopefully see
WSUS re-downloads the ESD then give it another try.
Edited by
Nick Bitzan

Reply | Quote
Nick Bitzan
5 Points
Pgina 20 de 32
1/12/16 18'33
After trying all of above mentioned solutions, re-installed SUP and for now everything
seems to be working fine.
First time we can use 1607 servicing.
Sign in
to vote
Edited by
SCCMNewbie12
Friday, September 02, 2016 2:32 AM

Reply | Quote
SCCMNewbie12
0 Points
Did you do a complete server rebuild (Reinstall OS, WSUS etc)?

or just remove the SUP role and reinstall?
0
Sign in
to vote

Reply | Quote
Trissy NSW
100 Points
We do not use SCCM also and We use WSUS only

What shall we do ?????
0
Sign in
to vote
Exactly my problem. I am not f$@%ing reinstalling WSUS and going through the
approving/declining process again.
Edited by
Martin P7

Reply | Quote
Martin P7 (Partner)
80 Points
Our WSUS enviroment is pretty big and thoroughly configured. I don`t want to reinstall
it now (2 days of work). It is not solution for us. But for somebody it can by satisfying.
0
Sign in
to vote
Exactly.
Reply | Quote
1
Sign in
to vote
Martin P7 (Partner)
80 Points
Another 0xc1800118 unhappy WSUS admin here.

I have WSUS only on Windows Server 2012 R2, SQL server on another server, updated
files stored on remote share and working fine.
Observed 0xc1800118 on a test computer.
After lots of work with this here is my experience:
1. I removed KB3159706 from WSUS server and rebooted.
2. Did removal steps 1 and 2 from How to delete upgrades in WSUS WSUS Product
Team Blog including removal of version 1607 ( $s.SearchUpdates("version 1607") ).
3. Run server cleanup. Upgrades were gone from WSUS, free space increased
accordingly.
4. Reinstalled KB3159706 with all the postinstallation steps described in KB3159706
and including undescribed MIME type addition (tried both, octet-stream and the other
one as well) and rebooted.
5. Run steps 3 and 4 from the link in step 2.
Pgina 21 de 32
1/12/16 18'33
5. Run steps 3 and 4 from the link in step 2.

6. Approved "Feature update to Windows 10 Enterprise, version 1607, en-us" and saw
the computers from my test group a in the update report details as "Install"
7. Run manual sync.
8. Run update on client, wasn't found.
9. Run wssutil.exe reset
10. Run update on client again, started downloading, downloaded, installing, error
0xc1800118.
I don't know what else to do. It's good at least SCCM people can get this working but WSUS
only people can't - I haven't seen anyone who managed to fix it. Does the WSUS reinstall
require new database as well? I don't want to go through approval process for all the
products and categories again it's aprox. 2 days job.
We are software development company and I want the devs to have the option to play with
Linux / Bash shell but still no luck.
This test computer was Windows 8 updated to Windows 8.1 updated to Windows 10 from
ISO with keep all and is currently on version 1511. Here's the full paste of setupact.log and
here is the setuperr.log:
2016-09-02 11:07:57, Error
SP
resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat:
The system cannot find the file specified. [0x00000002] __cdecl
2016-09-02 11:08:22, Error
key was provided.
2016-09-02 11:08:22, Error
Result = 0xC1800118
2016-09-02 11:08:22, Error
MOUPG
CDlpActionRecoverCrypto::ExecuteRoutine(2465): Result = 0xC1800118
2016-09-02 11:08:22, Error
CDlpObjectInternalImpl<class CUnknownImpl<class IDlpAction> > > >::Execute(441):
Result = 0xC1800118
2016-09-02 11:08:23, Error
0xC1800118
2016-09-02 11:08:23, Error
MOUPG CDlpTask::ExecuteActions(3397): Result =
0xC1800118
2016-09-02 11:08:23, Error
MOUPG CDlpTask::Execute(1631): Result =
0xC1800118
2016-09-02 11:08:23, Error
= 0xC1800118
2016-09-02 11:08:23, Error
= 0xC1800118
2016-09-02 11:08:23, Error
MOUPG CSetupManager::ExecuteInstallMode(690):
Result = 0xC1800118
2016-09-02 11:08:23, Error
MOUPG
CSetupManager::ExecuteDownlevelMode(391): Result = 0xC1800118
2016-09-02 11:08:25, Error
SP
resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat:
The system cannot find the file specified. [0x00000002] __cdecl
2016-09-02 11:08:28, Error
MOUPG CDlpTask::Cancel(979): Result =
0xC1800104
2016-09-02 11:08:28, Error
0xC180010A
2016-09-02 11:08:28, Error
0xC1800104
2016-09-02 11:08:28, Error
MOUPG CSetupManager::Execute(236): Result =
0x80248008
2016-09-02 11:08:28, Error
MOUPG CSetupHost::Execute(372): Result =
0x80248008
I don't think there a combination of steps people talk about I haven't tried. I am fiddling
with this crap for more over a week already. Microsoft, get your shit together for f..ks sake!
Pgina 22 de 32
1/12/16 18'33
Edited by
Martin P7

Reply | Quote
Martin P7 (Partner)
80 Points
Hi all!
RecoverCrypto: File is encrypted, but no key was provided.
1
Sign in
to vote
I`ve fixed this by reinstalling WSUS, WID, IIS

My Win10 clients are successfully upgraded to 1607 (Server 2012 R2 - WSUS)
My Steps:
Uninstall Role "WSUS" and under Features "Windows Update Services Tools"
Open "SQL Server Management" and connect to "Windows Internal Database" and
delete "SUSDB Database"
Uninstall Role "IIS" and Feature "Windows Process Activation Service", "Windows
Internal Database"
Reboot
Delete Folder "WsusContont" and "UpdateServicesPackages"
Delete Folder "C:\Program Files\Update Services"
Delete or rename Folder "C:\Windows\WID"
Delete or rename Folder "C:\inetpub"
Delete key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services"
Install KB3095113 (if not installed previously)
Reboot
Install Role "WSUS (with all the Components)" and Feature "HTTP Activation" under
".net Framework 4.5"
In Server Manager finish the installation of WSUS (WSUS is now installed)
In IIS add MIME typ ".esd application/octet-stream" for "WSUS Administration Site"
Run iisreset
Open WSUS Console finish the Wizard (under Product and Classification check
Windows 10 and Upgrades)
Sync
I hope i can help you!
Edited by
Paz2016
Friday, September 02, 2016 1:21 PM

Reply | Quote
Paz2016
25 Points
After trying all of above mentioned solutions, re-installed SUP and for now everything
seems to be working fine.
First time we can use 1607 servicing.
Sign in
to vote
When you reinstalled SUP did you have to redo all of your ADR's?
Reply | Quote
Nick Bitzan
5 Points
Pgina 23 de 32
1/12/16 18'33
Hi,
0
Sign in
to vote
Open "SQL Server Management" and connect to "Windows Internal Database" and delete
"SUSDB Database"
so you had to go through the approval process all over again? That's not good.
Edited by
Martin P7
Monday, September 05, 2016 6:47 AM

Reply | Quote
Martin P7 (Partner)
80 Points
I have an official statement from Microsoft that the know this issue.<o:p></o:p>
The are searching for a solution. There is no real workaround. <o:p></o:p>
0
Sign in
to vote
The only thing you can try is:<o:p></o:p>

Stop Windows update service -> delete under C:\Windows\SoftwareDistribution the folder DataStore > Start Windows Update Service -> Try again to install the update.<o:p></o:p>
When this "workaround" is not working, then is no solution available for you right now.<o:p></o:p>
I will post the solution when I have the feedback from MS<o:p></o:p>
Thursday, September 08, 2016 8:53 AM

Reply | Quote
Ps1_2012
10 Points
Just to be clear PS1_2012 - You are NOT referring to the "RecoverCrypto: File is
encrypted, but no key was provided." issue, correct?
0
Sign in
to vote

Reply | Quote
Andrew Westh
0 Points
Same problem here:

on WSUS Server (2012R2) the update KB3159706 was installed in july.
0
Sign in
to vote
At the beginning of september I approved the 1607 upgrade on WSUS and clients were
giving the error 0x80244019.
So I added the MIME type (.esx > octet-stream) in IIS and now the le is downloaded on client, but it
gives error 0x1800118 while trying to install
Andrea

Reply | Quote
Andrea Corti
0 Points
Pgina 24 de 32
1/12/16 18'33
Same here, just to add another voice and a bump.

Reply | Quote
OffColour1972
Sign in
to vote
60 Points
Same problem here too:

New test WSUS Server (2012 R2) just installed on a new 2012 R2 VM
0
Sign in
to vote
KB3159706 installed and post install performed including mime type .esd =
application/octet-stream
Only selected windows 10 OS selected upgrade classification
Added 1 OU with test computers through GP

0x1800118 error...
Waited for today's updates, applied all applicable, still get the same error so nothing new
with 9/13/16 updates!

Reply | Quote
vegas001
15 Points
We have same issue with our Windows 10 Pro 1511 workstations. About 100 computers
cannot upgrade to version 1607 because of error 0xc1800118. We tried to do clean install
of WSUS on Windows 2012 R2 with all updates mentioned on internet or this thread, added
.esd extension to IIS and everything but still nothing. So now we are just waiting for
microsoft to fix this problem.
Sign in
to vote
Wednesday, September 14, 2016 8:59 AM

Reply | Quote
garmada
0 Points
Hello,
0
Sign in
to vote
same problem here. I installed KB3095113 and KB3159706, added .esd Mime type, cleaned
WSUS, resynced, redownloaded 1607, still 0xC1800118 on all W10 Workstations.
We have a WSUS-only Environment, WSUS is installed on Windows Server 2012.
We have a poor Internet Connection, so i hope there is a way to fix this problem without
having to reinstall the WSUS role.
Wednesday, September 14, 2016 3:10 PM

Reply | Quote
Andreas Heiermann-Schille
0 Points
Pgina 25 de 32
1/12/16 18'33
Update SCCM client on the Windows 10 machine.

VISTA / XP Support Trainer
0
Sign in
to vote

Reply | Quote
Chanderjeet What is this work you sp...
10 Points
Update SCCM client on the Windows 10 machine.

VISTA / XP Support Trainer
0
Sign in
to vote
Already done that. Makes no difference.

Reply | Quote
OffColour1972
60 Points
Pgina 26 de 32
1/12/16 18'33
Hello,
0
Sign in
to vote
same problem here. I installed KB3095113 and KB3159706, added .esd Mime type,
cleaned WSUS, resynced, redownloaded 1607, still 0xC1800118 on all W10
Workstations.
We have a WSUS-only Environment, WSUS is installed on Windows Server 2012.
We have a poor Internet Connection, so i hope there is a way to fix this problem without
having to reinstall the WSUS role.
I have reinstalled WSUS, WID and IIS
Steps:
Uninstall Role "WSUS" and under Features "Windows Update Services Tools"
Open "SQL Server Management" and connect to "Windows Internal Database" and
delete "SUSDB Database"
Uninstall Role "IIS" and Feature "Windows Process Activation Service", "Windows
Internal Database"
Reboot
Delete Folder "WsusContont" and "UpdateServicesPackages"
Delete Folder "C:\Program Files\Update Services"
Delete or rename Folder "C:\Windows\WID"
Delete or rename Folder "C:\inetpub"
Delete key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services"
Reboot
Install Role "WSUS (with all the Components)" and Feature "HTTP Activation" under
".net Framework 4.5"
In Server Manager finish the installation of WSUS (WSUS is now installed)
In IIS add MIME typ ".esd application/octet-stream" for "WSUS Administration Site"
Run iisreset
Open WSUS Console finish the Wizard (under Product and Classification check
Windows 10 and Upgrades)
Sync
If your Client upgraded successfully, then you have to install KB3189866 manually (solve
WSUS BUG)
If you dont install this update, your PC cannot receive updates from WSUS
I have installed KB3189866 per Startscript on 40 Client (vers 14393.0 -> 14393.187)
All of my Client are on 14393.187 and work with WSUS
Edited by
Paz2016

Reply | Quote
Paz2016
25 Points
Pgina 27 de 32
1/12/16 18'33
Niall mentioned in this post that the Microsoft PG is aware and working on a fix.
https://www.windows-noob.com/forums/topic/14510-file-is-encrypted-but-no-key-wasprovided-trying-to-upgrade-win10-1511-to-1607-via-cm-cb-1606/
0
Sign in
to vote
Paz2016, we want to upgrade from 1511 to 1607 so it`s not possible to install KB3189866
on a Win10 1511 Client!? In a production environment it`s not possible to uninstall the
whole WSUS incl. SUP (and perhaps also IIS). Also some people are posting even if they
reinstalled everything it`s still not working, so we need a real fix or a working Workaround.
I tried to get in touch with David Jammer in twitter but no answer.
Jakob
Monday, September 19, 2016 12:03 PM

Reply | Quote
0
Sign in
to vote
Jakob_redtoo redtoo (Partner)
10 Points
Niall mentioned in this post that the Microsoft PG is aware and working on a fix.
https://www.windows-noob.com/forums/topic/14510-file-is-encrypted-but-no-keywas-provided-trying-to-upgrade-win10-1511-to-1607-via-cm-cb-1606/
Paz2016, we want to upgrade from 1511 to 1607 so it`s not possible to install
KB3189866 on a Win10 1511 Client!? In a production environment it`s not possible to
uninstall the whole WSUS incl. SUP (and perhaps also IIS). Also some people are posting
even if they reinstalled everything it`s still not working, so we need a real fix or a
working Workaround. I tried to get in touch with David Jammer in twitter but no answer.
Jakob
we have over 1000 Clients. i reinstalled the whole WSUS, WID, Webserver an it works.
If your Client on 1607, you have to install KB3189866 (solve WSUS BUG).
Tuesday, September 20, 2016 6:36 AM

Reply | Quote
Paz2016
25 Points
I tried everything, reinstall WSUS, SUP etc... The only way it worked for me is to delete the
datastore.edb in C:\Windows\SoftwareDistribution\Datastore folder on the client. I don't
think this is recommended.
0
Sign in
to vote
Edited by
HEALTH_DISCO

Reply | Quote
HEALTH_DISCO
0 Points
Pgina 28 de 32
1/12/16 18'33
0
Sign in
to vote
I tried everything, reinstall WSUS, SUP etc... The only way it worked for me is to delete
the datastore.edb in C:\Windows\SoftwareDistribution\Datastore folder on the client. I
don't think this is recommended.
Yes after you reinstalled WSUS, WID etc, you have to remove the client database.
I renamed the whole SoftwareDistribution folder

Reply | Quote
Paz2016
25 Points
RecoverCrypto: File is encrypted, but no key was provided.
0
Sign in
to vote
I`ve fixed this by reinstalling a new WSUS and SUP in my lab. Hope that it helps to someone
else.
1. New server 2012 R2 fully patched
2. Installed WSUS and necessary updates (KB3159706)
3. Did not add the .ESD MIME setting to IIS server which WSUS is used.
4. Installed SUP in this new server.
5. Deployed the W10 update 1607
After doing all these, it was still failing..
Last thing I tried is: On the client where it failed numerious times; I did :
Stop service Windows Update
Delete the folder C:\Windows\SOFTWAREDISTRIBUTION
Start the service Windows Update
After doing these 3 steps, returned back to Software Center; tried to reinstall the update
1607.
Unfortunately after running 15sec. I saw the message "INSTALLED". Then my deployment
got totaly removed from the software center. So I realized that WSUS did not liked what I did
with the folder I deleted (Yeah, cause I deleted local WSUS database which was stored there)
So via Configuration manager control panel applet, I did run Software Updates Scan cycle
and waited for 10 min. Then I did run Software updates Deployment Evalaution cycle. Then
my deployment of update 1607 appeared back in software center.
When I click install It went and installed the upgrade.
So it is not only enough doing everything necessary on the server side, BUT there are also
some things needs to be done on the W10 client side.

Reply | Quote
Tolga S. KAYA Infosys
55 Points
Pgina 29 de 32
1/12/16 18'33
First powershell like solution from MS:

https://support.microsoft.com/en-us/kb/3194588
5
Sign in
to vote
Many thanks to gamb13r

http://answers.microsoft.com/en-us/profile/fc39381b-5687-46f9-84a4d2e31d7d9421#user-profile-tab-profile
Edited by
CSAD Florenc

Reittier

Reply | Quote
CSAD Florenc
60 Points
Thanks for that. Works perfectly even in an SCCM environment.
0
Sign in
to vote
Just made the classification changes in SCCM against the SUP and gave it time to
syncronise.
Thanks!

Reply | Quote
Trissy NSW
100 Points
Worked for me! Thanks!

Reply | Quote
Reittier netlogix (Partner)
35 Points
Sign in
to vote
Didn't work for me - I have still 128 "bad" updates...

USE SUSDB;
0
Sign in
to vote
SET NOCOUNT OFF;

select TotalResults = Count(*)
from tbFile
where (IsEncrypted = 1 and DecryptionKey is NULL) or (FileName like '%14393%.esd' and
IsEncrypted = 0)

Reply | Quote
dussan
0 Points
Andrew Westh
0 Points
For what its worth, here is another "this worked for me".
0
Sign in
to vote
Reply | Quote
Pgina 30 de 32
1/12/16 18'33
Hello
In addition to the article
0
Sign in
to vote
https://support.microsoft.com/en-us/kb/3194588
This blog was updated for this issue

https://blogs.technet.microsoft.com/wsus/2016/09/21/resolving-error-0xc1800118/
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and
confers no rights.

Reply | Quote
Darrell Gorter Microsoft
11,485 Points
Same trouble - still have 40 BAD updates.
0
Sign in
to vote
If Iremove (select FileDigest from tbFile where FileName like '%14393%.esd' except select
FileDigest from tbFileForRevision) from last query, it's failed. How can I remove them?
UPDATE: Fixed. When you run $1607Updates = $s.SearchUpdates("version 1607") you
should also change language of word "version" to your local.
Edited by
Alexey Litvinov

Reply | Quote
Alexey Litvinov
100 Points
This worked for me. Although I'm not sure if I was running the powershell script wrong,
but this section:
0
Sign in
to vote
declare @NotNeededFiles table (FileDigest binary(20) UNIQUE);

insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like
delete from tbFileOnServer where FileDigest in (select FileDigest from @NotNeededFiles)
delete from tbFile where FileDigest in (select FileDigest from @NotNeededFiles)
This wouldn't work for me in powershell which is when I noticed it was SQL.
So I manually ran it in SQL Management Studio, then ran the last two powershell lines once
the SQL part was completed.
Monday, September 26, 2016 7:06 PM

Reply | Quote
ParadingLunatic
5 Points
Pgina 31 de 32
1/12/16 18'33
At first this didn't work for me.
0
Sign in
to vote
I figured out my first problem was: when I copy and pasted directly from the website into
powershell it wouldn't delete the updates.. pasted into notepad then powershell and then it
worked for me.
After it was done I re-ran the sql query, and I had 32 bad updates again. this time I re-ran
all of the steps.
before I re-enabled the upgrade class, I redid the command needed for KB3159706
("C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing)
re-enabled upgrade class and re-synced WSUS and it worked this time.
For SCCM: I re-enabled the upgrades class from Site configuration -> Sites -> Configure
Site Components -> Software Update Point -> Classifications .... and I was able to push out
the servicing for 1607 and my clients are now getting the update.

Reply | Quote
Nick Bitzan
5 Points
We had success with following the steps in that KB article. What was different from what we
had already tried before that were the SQL commands they list to delete the update entries
from the SUSDB.
0
Sign in
to vote
declare @NotNeededFiles table (FileDigest binary(20) UNIQUE);

insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like
delete from tbFileOnServer where FileDigest in (select FileDigest from @NotNeededFiles)
delete from tbFile where FileDigest in (select FileDigest from @NotNeededFiles)
Edited by
TestValleySchool

Reply | Quote
0
Sign in
to vote
TestValleySchool
30 Points
Out of interest what SCCM client agent are you running? I spent some time trying to
troubleshoot this issue over the last couple of days and it appears 5.00.8355.1307 and
below suffer this issue. Try updating the client agent to 5.00.8412.1307 and see if this
fixes your issue. There appears to be some sort of compatibility problem. More info here:
http://simonbond.net/?p=407
Hope this helps
Thursday, November 10, 2016 11:56 AM

Reply | Quote
Newsletter | Contact Us | Privacy Statement | Terms of Use | Trademarks | Site Feedback
SJBond Bondytech
75 Points
2016 Microsoft. All rights reserved.
Pgina 32 de 32

1511 To 1607 Enterprise Feature Upgrade Failing

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

1511 To 1607 Enterprise Feature Upgrade Failing

Enviado por

Direitos autorais:

Formatos disponíveis

1511 to 1607 Enterprise feature upgrade failing

United States (English)

Search TechNet with Bing

Search related threads

Search forum questions