RecoverCrypto: File is encrypted, but no key was provided

Windows 10 1607 feature update will fail when deployed with SCCM Current Branch 1606.

The following error will be displayed in C:\$Windows.~BT\Sources\Panther\setupact.log

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

MOUPG  CDlpActionRecoverCrypto::DoCrypto(1713): Result = 0xC1800118

 

WUAHandler.log will show;

Upgrade installation result indicates that commit cannot be done. 

Installation job encountered some failures. Error = 0x80240022. Commit Result = 0x00000001.

We will receive above error even after installing KB3159706 with post installation steps.

I think the post installation steps are incomplete and not documented very well.

After installing the KB3159706, the SUP need to be uninstalled and re-installed.

This will fix the error File is encrypted, but no key was provided problem.

If remediating an existing environment, the best thing will be;

-          Uninstall WSUS

-          Delete SUP database

-          Remove WSUS folder

-          Uninstall SUP

-          Reboot the server

-          Delete the Update services folder from C:\Program Files

-          Install WSUS

-          Install KB3095113 (If not installed previously)

-          Install KB3159706 (If not installed previously)

-          Reboot the server

-          Install SUP

If installing on a new environment

-          Install WSUS

-          Install KB3095113

-          Install KB3159706

-          Reboot the server

-          Install SUP

Once the SUP is successfully installed, create a new servicing plan and deploy the feature update.

This time the update will install without File is encrypted, but no key was provided.

Failed to copy Program Files\Microsoft Configuration Manager\bin\x64\smspxeperf.dll

You may receive below error msg when upgrading System Center Current Branch 1602 to 1606. (in fact in any SCCM version upgrade)

distmgr.log on the Primary site;
Failed to copy f:\Program Files\Microsoft Configuration Manager\bin\x64\smspxeperf.dll to \\SCCB-DP-W2012.LAB\SMS_DP$\sms\bin\smspxeperf.dll. GLE = 32
or
The distribution point ["Display=\\SCCB-DP-W2012.LAB \"]MSWNET:["SMS_SITE=SCB"]\\SCCB-DP-W2012.LAB \ is not installed or upgraded yet.
or
DP thread with ID 6096 failed to process DP action

Event Log on problem DP;
On the DP, Application event log will show "An error occurred while trying to load the module from \SMS_DP$\sms\bin\smspxe.dll for provider SMSPXE. If the provider is marked as critical, the Windows Deployment Services server will be shut down".
Error Information: 0x7F

This will break all the content distribution to the problem distribution point in SCCM.

Fix:
First check and compare the smspxeperf.dll on the primary site server with file on the problem DP.
If the versions won’t match, then rename the existing version on the DP.
If you get access denied error stop WDS service, then rename the smspxeperf.dll. Now copy the new file from primary server or CAS to the problem DP under \SMS_DP$\sms\bin\
You can wait for an hour to site server to re-run the DP upgrade or simply re-start the SMS_SITE_COMPONENT_MANAGER service on the primary site server. This will start the upgrade process straight away. Review the distmgr.log to see the progress of the upgrade.
Once the DP is upgraded try to distribute a simple package and that should get distributed without any issues.

Also review the \SMS_DP$\sms\bin\vcredist.log on the DP for any errors, as in many instances Visual Runtime install also caused the problem.

SCCM SQL Server vlogs

If we ever want to view the SQL logs to troubleshoot SCCM related issue, we can get information from SQL vlog.

To get top 1000 records from vlog;
SELECT TOP 1000 * FROM vLogs
NOTE: make sure you use top otherwise the SQL will get all the log entries and will cause perfomance issues.

To search vlogs log time in between days then ;
SELECT * FROM vLogs 
WHERE LogTime > '2016-07-25 12:00:00' and LogTime < '2016-07-26 12:00:00'
ORDER by LogTime desc

SCCM 1606 Step by Step Upgrade Guide

A week or so ago Microsoft has released Update1606 for System Center current branch.

The 1606 release notes can be found on Microsoft Enterprise Mobility and Security Blog

If SCCM 1606 update is not showing up in the console (most likely you are not in the release of first ring) and don’t want wait then get EnableUpdateRing.ps1 from Here

Launch PowerShell as administrator then run EnableUpdateRing.ps1 <Siteservername>

Note: Just use server name without FQDN.

You will get The command(s) completed successfully.

Now go to \Administration\Overview\Cloud Services\Updates and Servicing node in SCCM console, then run Check for updates.

After 10-15 min later, the console will show Configuration Manager 1606 and should be in downloading state;

The SMS_DMP_DOWNLOADER component will start downloading a large file and we can see download of a large file in dmpdownloader.log (<Install_DIR>\Microsoft Configuration Manager\Logs\);

Before upgrading the SCCM to 1606, the versions will be (1602);

          System Center Configuration Manager Version 1602

          Console Version: 5.0.8355.1306

          Site Version: 5.00.8355.1000

Once the download is completed, the console will show the state of Configuration Manager 1606 is Available

Now like any other previous updates, first run the Run Prerequisite check. Once the prerequisite check is passed then run Install Update Pack.

It will start the Configuration Manager updates wizard. Click next on the General tab

Select required features to be installed then click next;

Select required client update options then click next;

Accept the license terms then click next;

Review the selection options then click next;

Close the completion window. It will take 20-30 min (based on the server performance) to complete the update.

If we re-launch or check the console version, we will get a popup message saying A new version of the console is available (5.00.8412.100).

Click OK to upgrade the console.

Once the update is installed the version number of SCCM will be;

         System Center Configuration Manager Version 1606

         Console Version: 5.0.8412.1003

         Site Version: 5.0.8412.100

That’s It.

We have completed upgrading System Center Current Branch 1602 to System Center Current Branch 1606.

Click here for complete SCCM 1511 Current Branch setup step by step guide.

Click here for complete SCCM 1511 Current Branch step by step guide, step by step migration guide, step by step monitoring and health check guide and step by step SCCM Current Branch servicing guide.