none
1511 to 1607 Enterprise feature upgrade failing RRS feed

  • Question

  • 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

    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     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]


    • Edited by gemidriver Thursday, August 18, 2016 12:16 AM
    Thursday, August 18, 2016 12:10 AM

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.

    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 08:39:02, Info                  MOUPG  SetupManager::DetermineSetupPhase: CurrentSetupPhase [SetupPhaseUnpack]
    2016-08-18 08:39:02, Info                  MOUPG  Setup phase change: [SetupPhaseUnknown] -> [SetupPhaseUnpack]
    2016-08-18 08:39:02, Info                  MOUPG  SetupManager::OpenOrCreateTask: Creating new task [Unpack].
    2016-08-18 08:39:02, Info                  MOUPG  CreateTask: Name = [Unpack], WorkingPath = [C:\$WINDOWS.~BT\Sources], TransportId = [00000000-0000-0000-0000-000000000000], Flags = [0x0]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Entering Prepare Method
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Leaving Prepare Method
    2016-08-18 08:39:03, Info                  MOUPG  UpgLayout: Entering Prepare Method
    2016-08-18 08:39:03, Info                  MOUPG  UpgLayout: Leaving Prepare Method
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Wim Source Path: [C:\$WINDOWS.~BT\Sources\Install.esd]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Wim Target Path: [NULL]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Remote Source Path: [NULL]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Crypto Key [No]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Size: [0x0]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Flags: [0x4]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Hash Type: [0]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing Hash Value: [NULL]
    2016-08-18 08:39:03, Info                  MOUPG  RecoverCrypto: Initializing DeleteSource Value: [FALSE]
    2016-08-18 08:39:03, Info                  MOUPG  SetupNotify::CleanupCachedFile - Cleaning up cached file [14393.0.160715-1616.rs1_release_CLIENTEducation_VOL_x64fre_en-us.esd].
    2016-08-18 08:39:03, Info                  MOUPG  SetupManager: InstallAttempts = [6]
    2016-08-18 08:39:03, Info                  MOUPG  DlpTask: Entering Execute Method
    2016-08-18 08:39:03, Info                  MOUPG  DlpTask: Transport not set. Skipping download phase.
    2016-08-18 08:39:04, Info                  MOUPG  DlpTask: Executing Actions...
    2016-08-18 08:39:04, Info                  MOUPG  Action execution thread timeout period: [1000 ms]
    2016-08-18 08:39:04, Info                  MOUPG  ProgressHandlerAction: Sending initial progress message for action [0].
    2016-08-18 08:39:04, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2002]
    2016-08-18 08:39:04, Info                  MOUPG  RecoverCrypto: Entering Execute Method
    2016-08-18 08:39:04, Info                  MOUPG  DlpTask: Resetting action [0] progress start time.
    2016-08-18 08:39:04, Error                 MOUPG  RecoverCrypto: File is encrypted, but no key was provided.
    2016-08-18 08:39:04, Error                 MOUPG  CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118
    2016-08-18 08:39:04, Error                 MOUPG  CDlpActionRecoverCrypto::ExecuteRoutine(2465): Result = 0xC1800118
    2016-08-18 08:39:04, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2101]
    2016-08-18 08:39:04, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2100]
    2016-08-18 08:39:04, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IDlpAction> > > >::Execute(441): Result = 0xC1800118
    2016-08-18 08:39:04, Info                  MOUPG  RecoverCrypto: Leaving Execute Method
    2016-08-18 08:39:04, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0xC1800118
    2016-08-18 08:39:04, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
    2016-08-18 08:39:04, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]
    2016-08-18 08:39:05, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0xC1800118
    2016-08-18 08:39:05, Info                  MOUPG  Waiting for actions thread to exit.
    2016-08-18 08:39:05, Info                  MOUPG  Actions thread has exited.
    2016-08-18 08:39:05, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
    2016-08-18 08:39:05, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]
    2016-08-18 08:39:05, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0xC1800118
    2016-08-18 08:39:05, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]
    2016-08-18 08:39:05, Info                  MOUPG  DlpTask: Leaving Execute Method
    2016-08-18 08:39:05, Error                 MOUPG  CSetupManager::ExecuteTask(2067): Result = 0xC1800118
    2016-08-18 08:39:05, Error                 MOUPG  CSetupManager::ExecuteTask(2030): Result = 0xC1800118
    2016-08-18 08:39:05, Error                 MOUPG  CSetupManager::ExecuteInstallMode(690): Result = 0xC1800118
    2016-08-18 08:39:05, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(391): Result = 0xC1800118
    2016-08-18 08:39:05, Info                  MOUPG  Setup phase change: [SetupPhaseUnpack] -> [SetupPhaseError]
    2016-08-18 08:39:05, Info                  MOUPG  SetupManager::OpenOrCreateTask: Found task [Exit] in state [0x6] - Action [0xFFFFFFFF].
    2016-08-18 08:39:05, Info                  MOUPG  SetupManager::OpenOrCreateTask: Deleting...
    2016-08-18 08:39:06, Info                  MOUPG  SetupManager::OpenOrCreateTask: Deleted task [Exit]
    2016-08-18 08:39:06, Info                  MOUPG  SetupManager::OpenOrCreateTask: Creating new task [Exit].
    2016-08-18 08:39:06, Info                  MOUPG  CreateTask: Name = [Exit], WorkingPath = [C:\$WINDOWS.~BT\Sources], TransportId = [00000000-0000-0000-0000-000000000000], Flags = [0x0]
    2016-08-18 08:39:06, Info                  MOUPG  Finalize: Entering Prepare Method
    2016-08-18 08:39:06, Info                  MOUPG  Finalize: Leaving Prepare Method
    2016-08-18 08:39:06, Info                  MOUPG  DlpTask: Entering Execute Method
    2016-08-18 08:39:06, Info                  MOUPG  DlpTask: Transport not set. Skipping download phase.
    2016-08-18 08:39:07, Info                  MOUPG  DlpTask: Executing Actions...
    2016-08-18 08:39:07, Info                  MOUPG  Action execution thread timeout period: [1000 ms]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing SetupResult: [0xc1800118]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing Extended:    [0x30002]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing Scenario:    [5]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing Mode:        [2]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing Target:      [C]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing SQM:         [TRUE]
    2016-08-18 08:39:07, Info                  MOUPG  ImageExit: Initializing PostReboot:  [FALSE]
    2016-08-18 08:39:07, Info                  MOUPG  ProgressHandlerAction: Sending initial progress message for action [0].
    2016-08-18 08:39:07, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2002]
    2016-08-18 08:39:07, Info                  MOUPG  Finalize: Entering Execute Method
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Loading Setup Platform...
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Determine if the expected version of Setup Platform has been loaded...
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Platform and Setup binaries match!
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Attempting resurrect of Setup Platform object...
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: Starting verification of footprint section Footprint.Basic
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: The requested footprint is present
    2016-08-18 08:39:07, Info                         SPGenerateCopyListFromConfigFile: Didn't find file list in C:\$WINDOWS.~BT\Sources\setupplatform.cfg, section Footprint.Servicing.amd64
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: Starting verification of footprint section Footprint.Servicing
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: The requested footprint is present
    2016-08-18 08:39:07, Info                         SPGenerateCopyListFromConfigFile: Didn't find file list in C:\$WINDOWS.~BT\Sources\setupplatform.cfg, section Footprint.ICB.amd64
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: Starting verification of footprint section Footprint.ICB
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: Could not find footprint file C:\$WINDOWS.~BT\Sources\mxeagent.dll
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: The requested footprint is not present
    2016-08-18 08:39:07, Warning                      SPGetFootprintCapabilities: Footprint [Footprint.ICB] incomplete; the platform capability will not be available
    2016-08-18 08:39:07, Info                         SPGenerateCopyListFromConfigFile: Didn't find file list in C:\$WINDOWS.~BT\Sources\setupplatform.cfg, section Footprint.Migration.amd64
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: Starting verification of footprint section Footprint.Migration
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: Could not find footprint file C:\$WINDOWS.~BT\Sources\hwcompat.dll
    2016-08-18 08:39:07, Info                         SPVerifyFootprint: The requested footprint is not present
    2016-08-18 08:39:07, Warning                      SPGetFootprintCapabilities: Footprint [Footprint.Migration] incomplete; the platform capability will not be available
    2016-08-18 08:39:07, Info                  SP     CSetupPlatform::Initialize: Setup log starts:
    2016-08-18 08:39:07, Info                         There is already a running setup user mode etw session!
    2016-08-18 08:39:07, Info                         VDS available
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Setup Platform object resurrected!
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Enable diagnosis mode
    2016-08-18 08:39:07, Info                         Key CollectTrace is not available.
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Persisting telemetry data
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Not persisting telemetry data
    2016-08-18 08:39:07, Info                  MOUPG  MoSetupPlatform: Resurrecting NewSystem object from [C:\$Windows.~BT\Sources]
    2016-08-18 08:39:07, Info                  SP     Attempting to resurrect a new system from C:\$Windows.~BT\Sources
    2016-08-18 08:39:07, 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 08:39:07, Warning               MOUPG  ImageExit: Unable to resurrect NewSystem object. hr=0x80070002
    

    Is there some way to validate the proper configuration of the KB3159706 post-install steps that we can do?

    Thursday, August 18, 2016 8:00 AM
  • I have same issue

    I have the following:

    -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

    Thursday, August 18, 2016 8:45 AM
  • Also I added the mime type ESD to the IIS to support it
    Thursday, August 18, 2016 8:53 AM
  • Same problem here, but randomly. 1/3 of machines cannot update.
    Thursday, August 18, 2016 10:55 AM
  • Same error 0xc1800118 here. None of founded tips and patches resolved problem, yet.
    Thursday, August 18, 2016 12:51 PM
  • 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.
    Thursday, August 18, 2016 1:09 PM
  • Also having the same error.

    The software change returned error code 0xC1800118(-1048575720).

    Thursday, August 18, 2016 8:37 PM
  • 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.
    Sorry, can`t confirm that. Many retries on more computers with no success.
    Friday, August 19, 2016 6:01 AM
  • 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.

    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.
    Friday, August 19, 2016 7:46 AM
  • Solution:

    http://moonlightsoft.blogspot.pt/2016/08/error-0x80244019-occurred-while.html

    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

    Friday, August 19, 2016 9:20 AM
  • 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.

    Friday, August 19, 2016 10:16 AM
  • Also having the same error.

    The software change returned error code 0xC1800118(-1048575720).

    Friday, August 19, 2016 11:41 AM
  • 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.


    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
  • 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

    • Edited by RedDevil BE Friday, August 19, 2016 3:10 PM
    Friday, August 19, 2016 2:58 PM
  • 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.


    KR. Jyrki

    • Proposed as answer by RedDevil BE Saturday, August 20, 2016 9:39 AM
    Friday, August 19, 2016 5:42 PM
  • Just as jyrppa noticed, the client version does matter.

    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 Saturday, August 20, 2016 9:56 AM
    • Proposed as answer by joshhmorg Tuesday, September 6, 2016 5:07 PM
    Saturday, August 20, 2016 9:39 AM
  • Verd odd as I have all this in place and still fails with the error
    Saturday, August 20, 2016 12:58 PM
  • Hi,

    I've got the same behavior like jyrppa.

    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
    Monday, August 22, 2016 6:43 AM
  • 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.

    Ive also tried adding the ".esd" "application/octet-stream", no change.

    2016-08-22 10:51:25, Error                 MOUPG  RecoverCrypto: File is encrypted, but no key was provided.

    SCCM client: 5.00.8412.1007


    • Edited by danbro92 Monday, August 22, 2016 9:37 AM
    Monday, August 22, 2016 9:30 AM
  • 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-your-configmgr-1606-sup-servers-to-deploy-the-windows-10-anniversary-update/ 
    Monday, August 22, 2016 9:52 AM
  • I got KB3159706 aswell with steps completed. Not using SSL.
    Monday, August 22, 2016 10:56 AM
  • 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 Monday, August 22, 2016 11:30 AM
    Monday, August 22, 2016 11:25 AM
  • 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.


    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
  • We continue to see the errors with no change in behaviour, even with the CM client on 5.00.8412.1007.
    Tuesday, August 23, 2016 7:23 AM
  • But what shall we do if we don't use SCCM as Update Source? We use WSUS.
    Tuesday, August 23, 2016 8:12 AM
  • We do not use SCCM also and We use WSUS only

    What shall we do ?????

    Tuesday, August 23, 2016 1:20 PM
  • I have the same problem. WSUS on Windows Server 2012 (not R2). We have 190 Windows 10 clients!

    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 failed: 0x1
    2016-08-24 07:49:57, Error                 SP     CSetupPlatform::ResurrectNewSystem: Cannot resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: Systém nemůže nalézt uvedený soubor. [0x00000002] __cdecl UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]
    2016-08-24 07:51:19, Error                 MOUPG  RecoverCrypto: File is encrypted, but no key was provided.
    2016-08-24 07:51:19, Error                 MOUPG  CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118
    2016-08-24 07:51:19, Error                 MOUPG  CDlpActionRecoverCrypto::ExecuteRoutine(2465): Result = 0xC1800118
    
    WindowsUpdate.log:
    2016. 08. 24 07:51:14.8174487 1028  9656  Agent           Updates to install = 1
    2016. 08. 24 07:51:14.8233793 1028  9656  Agent             Title = Aktualizace funkc?? Windows 10 Pro, verze 1607, cs-cz, maloobchodn?? vyd??n??
    2016. 08. 24 07:51:14.8233883 1028  9656  Agent             UpdateId = 803BEA9D-CD99-4263-AA1D-6C43CD15F4DD.201
    2016. 08. 24 07:51:14.8233887 1028  9656  Agent               Bundles 1 updates:
    2016. 08. 24 07:51:14.8233932 1028  9656  Agent                 8A4A5746-BDFA-4659-AD25-583D35E26AC8.201
    2016. 08. 24 07:51:15.6378869 1028  9656  Handler         Loaded state. m_dwState now: Setup360_CompatToolPhase2(9)
    2016. 08. 24 07:51:15.6503269 1028  6256  Misc            Got WSUS Client/Server URL: http://wsus.xxx.local:8530/ClientWebService/client.asmx""
    2016. 08. 24 07:51:15.6503881 1028  6256  ProtocolTalker  OK to reuse existing configuration
    2016. 08. 24 07:51:15.6503912 1028  6256  ProtocolTalker  Existing cookie is valid, just use it
    2016. 08. 24 07:51:15.6503921 1028  6256  ProtocolTalker  PTInfo: Server requested registration
    2016. 08. 24 07:51:15.6842552 1028  6256  Misc            Got WSUS Reporting URL: http://wsus.xxx.local:8530/ReportingWebService/ReportingWebService.asmx""
    2016. 08. 24 07:51:15.6843123 1028  6256  WebServices     Auto proxy settings for this web service call.
    2016. 08. 24 07:51:15.7119190 1028  9656  DownloadManager Preparing update for install, updateId = {8A4A5746-BDFA-4659-AD25-583D35E26AC8}.201.
    2016. 08. 24 07:51:15.7127107 6872  3192  Handler         * START *   Windows Setup Install
    2016. 08. 24 07:51:15.7127111 6872  3192  Handler         Updates to install = 1
    2016. 08. 24 07:51:15.7174132 6872  3192  Handler         Loaded state. m_dwState now: Setup360_CompatToolPhase2(9)
    2016. 08. 24 07:51:15.7179550 6872  3192  Handler         Starting Windows Setup with command line = C:\WINDOWS\SoftwareDistribution\Download\24f159089c605717843ec9233a637cf3\WindowsUpdateBox.exe" /ClassId 3d01c650-7a44-44e9-aea9-11bc20777378 /ReportId {8A4A5746-BDFA-4659-AD25-583D35E26AC8}.201 /Install /Update /ClientId d1020ace-529d-49dd-a572-0a3bb39dffd0"
    2016. 08. 24 07:51:15.7179563 6872  3192  Handler         HandlerSecsInADay = 86400.
    2016. 08. 24 07:51:15.7179572 6872  3192  Handler         Registering WinSetup COM server as CLSID {3D01C650-7A44-44E9-AEA9-11BC20777378} and APPID {407BB232-318A-4236-B4D5-74444C6B0E1F}
    2016. 08. 24 07:51:15.7207489 6872  3192  Handler         Successfully registered WinSetup COM server as CLSID {3D01C650-7A44-44E9-AEA9-11BC20777378}
    2016. 08. 24 07:51:16.1393673 6872  12992 Handler         Requested file 14393.0.160715-1616.rs1_release_CLIENTPRO_RET_x64fre_cs-cz.esd has no decrypt information
    2016. 08. 24 07:51:18.8141634 6872  12992 Handler         Deleting setup file '14393.0.160715-1616.rs1_release_CLIENTPRO_RET_x64fre_cs-cz.esd'
    2016. 08. 24 07:51:35.0995312 6872  3192  Handler         Installer completed. Process return code = 0x80248008, result = 0x80248008, callback pending = False
    2016. 08. 24 07:51:35.1000997 6872  3192  Handler         Handler: Setup360 returned unknown error 80248008 for state 9, resetting state to Unknown
    2016. 08. 24 07:51:35.1001015 6872  3192  Handler         State changed. was: Setup360_CompatToolPhase2(9), now: <invalid>(0)
    2016. 08. 24 07:51:35.1009672 6872  3192  Handler         Saved state. m_dwState: <invalid>(0)
    2016. 08. 24 07:51:35.1013496 6872  3192  Handler         Exit code = 0x80248008
    2016. 08. 24 07:51:35.1013519 6872  3192  Handler         * END *   Windows Setup Install
    2016. 08. 24 07:51:35.1031971 1028  9656  Handler         Loaded state. m_dwState now: <invalid>(0)
    2016. 08. 24 07:51:35.1257224 1028  9656  Agent           LogHistory called. idUpdate={803BEA9D-CD99-4263-AA1D-6C43CD15F4DD}.201, resultMapped=C1800118, resultUnMapped=80248008
    2016. 08. 24 07:51:35.1445514 1028  9656  Agent           Installing updates CallerId = UpdateOrchestrator
    2016. 08. 24 07:51:35.1445817 1028  16160 ComApi           Install ClientId = UpdateOrchestrator
    2016. 08. 24 07:51:35.1445835 1028  16160 ComApi          Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0
    2016. 08. 24 07:51:35.1446482 1028  16160 ComApi          Reboot required = False
    2016. 08. 24 07:51:35.1446486 1028  16160 ComApi          Exit code = 0x00000000; Call error code = 0x80240022
    2016. 08. 24 07:51:35.1446495 1028  16160 ComApi          * END *   Install ClientId = UpdateOrchestrator
    2016. 08. 24 07:51:35.1446513 1028  16160 Agent           WU client calls back to install call {6999483E-391A-43F5-86D6-29181C057DC7} with code Call complete and error 0
    2016. 08. 24 07:51:35.1490375 1028  15784 ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    Wednesday, August 24, 2016 6:58 AM
  • We are also seeing error 0xC1800118.

    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 Wednesday, August 24, 2016 8:32 AM
    Wednesday, August 24, 2016 8:27 AM

  • Well there you said it CalleW, it could very much be a Server 2012 (Not R2) problem. Im running without R2 aswell.
    Wednesday, August 24, 2016 8:45 AM
  • 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
    Wednesday, August 24, 2016 8:46 AM
  • 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.


    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 Wednesday, August 24, 2016 11:52 AM
    Wednesday, August 24, 2016 11:30 AM
  • 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?

    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.
    Wednesday, August 24, 2016 2:45 PM
  • 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 ?

    Step by Step Configuration Manager Guides > https://www.windows-noob.com/forums/topic/13288-step-by-step-guides-system-center-configuration-manager-current-branch/

    Thursday, August 25, 2016 1:35 PM
  • how can i delete those 1607 updates? 

    just deny them?

    • Proposed as answer by -Paz- Friday, August 26, 2016 5:48 AM
    • Unproposed as answer by -Paz- Friday, August 26, 2016 5:48 AM
    Friday, August 26, 2016 5:37 AM
  • Hi,

    i deleted the files by those steps:

    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 -Paz- Friday, August 26, 2016 5:48 AM
    Friday, August 26, 2016 5:48 AM
  • 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...
    Friday, August 26, 2016 9:41 AM
  • Hi Guys,

    we had same issue in various environments and the issue is now resolved.

    If you are receiving File is encrypted, but no key was provided, CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118, then it is time to re-install 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-but-no.html

    Cheers,

    Vneu

    Saturday, August 27, 2016 2:31 PM
  • Hi Guys,

    we had same issue in various environments and the issue is now resolved.

    If you are receiving File is encrypted, but no key was provided, CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118, then it is time to re-install 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-but-no.html

    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.
    Monday, August 29, 2016 6:34 AM
  • 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 ?

    Step by Step Configuration Manager Guides > https://www.windows-noob.com/forums/topic/13288-step-by-step-guides-system-center-configuration-manager-current-branch/

    Yup, confirmed.  Done all that, same issues.
    Monday, August 29, 2016 1:37 PM
  • same issue here too.

    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
  • and by resync you mean resync your SUP ? did these steps resolve the problem for you ?

    Step by Step Configuration Manager Guides > https://www.windows-noob.com/forums/topic/13288-step-by-step-guides-system-center-configuration-manager-current-branch/

    Tuesday, August 30, 2016 5:06 AM
  • Hi Guys,

    we had same issue in various environments and the issue is now resolved.

    If you are receiving File is encrypted, but no key was provided, CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118, then it is time to re-install 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-but-no.html

    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
  • At the frist try I recive the error 0xC1800118.

    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?

    Wednesday, August 31, 2016 9:13 AM
  • 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.?
    Wednesday, August 31, 2016 5:48 PM
  • Maybe this post helps to understand what may be going on.

    https://blogs.technet.microsoft.com/enterprisemobility/2016/08/05/update-your-configmgr-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 packagesand any subsequent Windows 10 feature upgrades

    I hope that this helps.


    Raul Systems Support

    Thursday, September 1, 2016 12:56 PM
  • 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 Thursday, September 1, 2016 2:22 PM
    Thursday, September 1, 2016 2:20 PM
  • At the frist try I recive the error 0xC1800118.

    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 Thursday, September 1, 2016 2:39 PM
    Thursday, September 1, 2016 2:39 PM
  • 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.

    After Installing KB3159706, I resynced WSUS, and then SCCM SUP. Deployments are downloading fine, however I’m getting the famous

    RecoverCrypto: File is encrypted, but no key was provided. In 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 didn’t 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 it’s 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_en-us.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 esd’s? without breaking WSUS?

    I’m thinking of repeating my process and this time delete these files and hopefully see WSUS re-downloads the ESD then give it another try. 



    Thursday, September 1, 2016 4:22 PM
  • 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.


    Friday, September 2, 2016 2:29 AM
  • Did you do a complete server rebuild (Reinstall OS, WSUS etc)? 

    or just remove the SUP role and reinstall?

    Friday, September 2, 2016 2:57 AM
  • We do not use SCCM also and We use WSUS only

    What shall we do ?????

    Exactly my problem. I am not f$@%ing reinstalling WSUS and going through the approving/declining process again.

    • Edited by Martin P7 Friday, September 2, 2016 6:58 AM
    Friday, September 2, 2016 6:57 AM
  • 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.

    Exactly.
    Friday, September 2, 2016 7:00 AM
  • 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.
    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     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-09-02 11:08:22, Error                 MOUPG  RecoverCrypto: File is encrypted, but no key was provided.
    2016-09-02 11:08:22, Error                 MOUPG  CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118
    2016-09-02 11:08:22, Error                 MOUPG  CDlpActionRecoverCrypto::ExecuteRoutine(2465): Result = 0xC1800118
    2016-09-02 11:08:22, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IDlpAction> > > >::Execute(441): Result = 0xC1800118
    2016-09-02 11:08:23, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 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                 MOUPG  CSetupManager::ExecuteTask(2067): Result = 0xC1800118
    2016-09-02 11:08:23, Error                 MOUPG  CSetupManager::ExecuteTask(2030): Result = 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     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-09-02 11:08:28, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
    2016-09-02 11:08:28, Error                 MOUPG  CDlpTask::Cancel(983): Result = 0xC180010A
    2016-09-02 11:08:28, Error                 MOUPG  CDlpTask::Cancel(979): Result = 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!

    • Edited by Martin P7 Friday, September 2, 2016 11:23 AM
    Friday, September 2, 2016 9:38 AM
  • Hi all!

    RecoverCrypto: File is encrypted, but no key was provided.

    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)
    • Install KB3159706 (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 -Paz- Friday, September 2, 2016 1:21 PM
    Friday, September 2, 2016 1:04 PM
  • 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.


    When you reinstalled SUP did you have to redo all of your ADR's? 
    Friday, September 2, 2016 1:13 PM
  • Hi,

    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 5, 2016 6:47 AM
    Monday, September 5, 2016 6:45 AM
  • 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>

    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 8, 2016 8:53 AM
  • Just to be clear PS1_2012 - You are NOT referring to the "RecoverCrypto: File is encrypted, but no key was provided." issue, correct?
    Thursday, September 8, 2016 7:40 PM
  • Same problem here:

    on WSUS Server (2012R2) the update KB3159706 was installed in july.

    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 file is downloaded on client, but it gives error 0x1800118 while trying to install


    Andrea

    Tuesday, September 13, 2016 1:09 PM
  • Same here, just to add another voice and a bump.
    Tuesday, September 13, 2016 3:09 PM
  • Same problem here too:

    New test WSUS Server (2012 R2) just installed on a new 2012 R2 VM

    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!

    Tuesday, September 13, 2016 10:15 PM
  • 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.
    Wednesday, September 14, 2016 8:59 AM
  • Hello,

    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
  • Update SCCM client on the Windows 10 machine.

    VISTA / XP Support Trainer

    Thursday, September 15, 2016 9:57 AM
  • Update SCCM client on the Windows 10 machine.

    VISTA / XP Support Trainer

    Already done that. Makes no difference.
    Thursday, September 15, 2016 3:49 PM
  • Hello,

    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"
    • Install KB3095113 (if not installed previously)
    • Install KB3159706 (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

    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 -Paz- Friday, September 16, 2016 9:15 AM
    Friday, September 16, 2016 9:15 AM
  • 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-was-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

    Monday, September 19, 2016 12:03 PM
  • 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-was-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
  • 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.
    • Edited by HEALTH_DISCO Tuesday, September 20, 2016 3:05 PM
    Tuesday, September 20, 2016 3:05 PM
  • 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

    Wednesday, September 21, 2016 1:41 PM
  • RecoverCrypto: File is encrypted, but no key was provided.

    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.

    Wednesday, September 21, 2016 10:33 PM
  • First powershell like solution from MS:

    https://support.microsoft.com/en-us/kb/3194588

    Many thanks to gamb13r
    http://answers.microsoft.com/en-us/profile/fc39381b-5687-46f9-84a4-d2e31d7d9421#user-profile-tab-profile
    • Edited by CSAD Florenc Thursday, September 22, 2016 6:31 AM
    • Proposed as answer by Reittier Friday, September 23, 2016 6:21 AM
    Thursday, September 22, 2016 6:25 AM
  • Thanks for that. Works perfectly even in an SCCM environment.

    Just made the classification changes in SCCM against the SUP and gave it time to syncronise.

    Thanks!

    Friday, September 23, 2016 4:46 AM
  • Worked for me! Thanks!
    Friday, September 23, 2016 6:21 AM
  • Didn't work for me - I have still 128 "bad" updates... 

    USE SUSDB; 

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

    Friday, September 23, 2016 6:32 AM
  • For what its worth, here is another "this worked for me". 
    Friday, September 23, 2016 1:50 PM
  • Hello

    In addition to the article

    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.

    Friday, September 23, 2016 7:05 PM
  • Same trouble - still have 40 BAD updates.

    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.
    Monday, September 26, 2016 6:39 AM
  • This worked for me.  Although I'm not sure if I was running the powershell script wrong, but this section:

    declare @NotNeededFiles table (FileDigest binary(20) UNIQUE);
    insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like '%14393%.esd'  except select FileDigest from tbFileForRevision);
    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
  • At first this didn't work for me.

    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. 


    Wednesday, September 28, 2016 4:03 PM
  • 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.

    declare @NotNeededFiles table (FileDigest binary(20) UNIQUE);
    insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like '%14393%.esd'  except select FileDigest from tbFileForRevision);
    delete from tbFileOnServer where FileDigest in (select FileDigest from @NotNeededFiles)
    delete from tbFile where FileDigest in (select FileDigest from @NotNeededFiles)


    Thursday, September 29, 2016 12:43 PM
  • 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://bondy.tech/?p=355

    Hope this helps


    • Edited by SJBond Tuesday, August 1, 2017 10:53 AM
    Thursday, November 10, 2016 11:56 AM
  • We had SCCM 1602 configured to dump a CBB (1607) update to an SU DP via Servicing Ring. I believe this probably occured in late December or early January. We are running WSUS integration with a separate DB, not a WID.

    I then ran Windows update on the site servers before upgrading the site to 1610. This is when our WSUS box got KB3159706. At this point the site is at 5.00.8458.100 and all clients are 5.00.8458.1007 running 1511. I had to remove and re-add the SUP role after the site upgrade to get WSUS to work properly again.

    We decided to start piloting the CBB upgrade this week when we noticed we were seeing the 0xC1800118 errors with references to the following errors:

    -MOUPG  RecoverCrypto: File is encrypted, but no key was provided.

    -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]

    -MOUPG  SetupNotify::Remapping missing decrypt key error [0xC1800118] -> [0x80248008]

    -MOUPG  SetupNotify::Leaving well-known error [0x80248008] as-is for WU/Store

    I completed the post install tasks for the hotfix, having to edit the Web.Config file, as well as adding the .esc MIME type to IIS. I then confirmed that I could launch the WSUS console, closed it, and re-sync'd the catalog via SCCM console. I then re-ran the service ring plan, cleaned up ccmcache, the SoftwareDistribution and $Windows.BT directories, and we're still seeing this error.

    I ran the SQL query to check the state of the WSUS DB and it returned 995 entries! Since we are integrated with SCCM using a separate DB, the fix is a little confusing to me. I know I need to disable the "upgrades" category, run some cleanup queries directly on the DB and possibly run some PS scripts, but after reviewing all the posts where people have gone to great lengths to fix this and still have problems, I'm more inclined to focus my efforts elsewhere. We don't have any plans to deploy the 1607 upgrade, rather we will re-image everything this Summer to 1607 or 1702 and will run down the next CBB update, assuming it too won't be broken at that time. Does anyone have specific steps for a fix in our particular scenario?

    Tuesday, March 7, 2017 3:47 PM
  •  Try the Workaround in this article:       

    https://support.microsoft.com/en-us/help/3194588/-0xc1800118-error-when-you-push-windows-10-version-1607-by-using-wsus

    Symptoms

    • You have Windows Server Update Services (WSUS) configured in your environment.
    • On the WSUS server, you install update 3159706 to enable decryption of the new feature update for Windows 10.
    • You approve the feature update for Windows 10 Version 1607.
    • You notice that WSUS clients detect and download the feature update to C:\Windows\ccmcache, and that files populate correctly in C:\Windows\SoftwareDistribution\DataStore.
    In this scenario, the installation starts, and files are decompressed to C:\$Windows.~BT. However, the process fails and returns the following error code:

    0xC1800118  

    Cause         
    This problem occurs if the Windows 10 Version 1607 update is encrypted but does not appear as encrypted in the WSUS Database. The problem may occur if the updates are synced before you apply KB3159706.


    • Edited by Tuckwell Tuesday, April 11, 2017 2:37 AM Formating for easier reading
    • Proposed as answer by Tuckwell Tuesday, April 11, 2017 11:33 PM
    Monday, April 10, 2017 11:01 PM
  • If it STILL fails check that the following Group Policy setting is NOT preventing the OSUpgrade:

    Computer Configuration / Administrative Templates / Windows Components / Windows Update Policy
    Setting: Turn off the upgrade to the latest version of Windows through Windows Update

    The corresponding registry key is:
    HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    DWORD value: DisableOSUpgrade = 1

    • Proposed as answer by Tuckwell Tuesday, April 11, 2017 11:33 PM
    • Unproposed as answer by Tuckwell Tuesday, April 11, 2017 11:33 PM
    • Proposed as answer by Tuckwell Tuesday, April 11, 2017 11:33 PM
    Tuesday, April 11, 2017 4:41 AM
  • Still failing for me on all Win 10 pcs and surfaces. Followed the original kb instructions about modding the webconfig file afterwards and had to bind the certificate again in iis since i have wsus going over ssl, added the esd mime type at the root, install sql mgmt console, removed all 1607 and 1703 updates from the db, ran powershell script for all of 1607 and 1703 updates. Resyncd. Cleared datastore folder and all downloads. Repeated entire process twice. Still getting 0xc1800118. 

    Server 2012 not R2 WSUS

    Friday, June 2, 2017 10:58 PM
  • Please follow the below article

    https://support.microsoft.com/en-us/help/3194588/0xc1800118-error-when-you-push-windows-10-version-1607-by-using-wsus

    But note the following:

    In this part

    Detect whether WSUS is in a bad state. To do this, run the following query:

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

    This number '%14393%.esd' refers to the Build Number, in this case it is Windows 10 Version 1607 (Anniversary Update)

    If your issue is with the 1703 version, then you need to replace it with "15063"

    The same applies to the below step as well, you need to replace the build number to match your needs

    // delete files from tbFile table (run on database)
    declare @NotNeededFiles table (FileDigest binary(20) UNIQUE);
    insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like '%14393%.esd'  except select FileDigest from tbFileForRevision);
    delete from tbFileOnServer where FileDigest in (select FileDigest from @NotNeededFiles)
    delete from tbFile where FileDigest in (select FileDigest from @NotNeededFiles)

    Say for example you are having issue updating from 1607 to 1703, then you will use the build number for the 1703 version

    The below steps summarize all:

    1- Remove the Upgrade Classification from the SCCM and WSUS

    2- You have to delete anything related to the problematic update such as "Deployment, Servicing Plan, Deployment Package, Deployment Package Folder, and the above script to remove the content from the database"

    3- Synchronize the updates from the SCCM console

    4- Reboot the Server

    5- Run the query that detects whether WSUS is in a bad state and make sure that the result is 0

    6- Re-enable the upgrade classification

    7- Run Synchronization again from SCCM, you will have to wait some time before you be able to download and deploy the feature update

    8- Clear the CCM Cache from the client, delete Windows~BT folder in C:\ Drive, Stop Windows Update Service, and then delete the Update DataStore as mentioned in the KB article

    It will work definitely


    Hussien Sherief

    Tuesday, July 18, 2017 5:26 AM
  • it could be with Client Version. If you just upgraded your SCCM and your clients were not fully upgraded to the latest version then it fails. upgrade your client and run again and it should work.

    Ratanpriya Sharma

    Monday, October 23, 2017 8:28 PM