SftzCeM6KiI/WZQ_1VTdt7I/AAAAAAAAAsw/gHZiG8a3vyUu95QIz529FSXHi97ADhVYwCLcBGAs/s1600/1%2529%2BPending%2BRestart%2BGUI.PNG' alt='Software Microsoft Windows Currentversion Windowsupdate Auto Update Rebootrequired' title='Software Microsoft Windows Currentversion Windowsupdate Auto Update Rebootrequired' />System Center Configuration Manager. Scenario Upgrading a Configmgr 2. RTMSP1R2 environment to a new R2 SP1 environment will end up into broken applications in your Task sequences with error 6. Welcome to the Microsoft Windows Vista Communities site. Windows Update being reoffered Ive provided you with some troubleshooting to clear a few registry. Now you just need to know where the pending reboot location is. There are a couple of places to check. HKLMSOFTWAREMicrosoftWindowsCurrentVersion. Unfortunately Microsoft doesnt provide a mechanism to determine the cumulative update version. Since they dont really provide operating system service packs any. HKLMSOFTWAREMicrosoftWindowsCurrentVersion GetItemProperty Path key Name ProgramFilesDir. ProgramFilesDir Ive never liked how this was provider. Issue After the upgrade was successfully performed, suddenly all applications within my OSD task sequence start failing with the following error code The task sequence failed to install application Intel Management Engine 6. Scope. Id6. 7A2. E3 6. F0 4. 7D4 AA5. A BB3. EC2. FApplication2. Install HW Driver Applications for HP8. A4b0.jpg' alt='Software Microsoft Windows Currentversion Windowsupdate Auto Update Rebootrequired' title='Software Microsoft Windows Currentversion Windowsupdate Auto Update Rebootrequired' />P in the group with exit code 6. The operating system reported error 6. The password provided is too short to meet the policy of your user account. Please choose a longer password. To be honest with my blog readers, this particular message can be caused by multiple reasons. I will list all possible solutions workarounds that I have come across to solve this issue. Cause 1 Applications have no Content. ID associated I blogged about this beginning of 2. After some checks, I saw that it concerned only applications and I discovered that had no Content. ID associated to each Deployment Type. In other words, all the applications created and that are embedded in a TS with no direct deployments attached to the Application. It appears that the upgrade process broke all applications. You can confirm this with the Application Catalog downloads as well. You will see Did not detect app deployment type in the App. Discovery. log file. Additionally, the Software Center will show the error message Failed. Clicking on the details will result in The software change returned error code 0x. D0. 06. 07 2. 01. We found as workaround, you have simply to add a comment to each DT and it will update the content ID. Nevertheless, the change means that a redistribution of your application on all your DPs. Following the steps as further discussed in this blog post at http scug. Cause 2 Corrupt task sequence In some cases the policy that is related to the task sequence gets corrupt. This can be easily solved by creating a brand new task sequence and copying the steps from the older one side by side. Delete the old task sequence create a new deployment for the just newly created task sequence. Cause 3 SMSMP parameter set incorrect I had also had problems after upgrading to SCCM R2 SP1. I was not able to install any applications as part of a task sequence as they all failed with error 6. Installing applications outside of a Task sequence did work normally. The status message reported was exactly the same as described above 6. Password too short. After investigating the client side log files it turned out, that the SCCM client was trying to download the application package using https first and after a few retrys would switch to http only. Because my DP is configured to accept http and https as like default behavior. I fixed the Problem by changing the value of the SMSMP parameter in the Task sequence step Setup Windows and Configuration Manager from. SMSMPmyserver. mydomain. SMSMPhttp myserver. After this change, application installation worked as expected again. Cause 4 FIPS has been enabled Enabling FIPS mode makes Windows and its subsystems use only FIPS validated cryptographic algorithms. An example is Schannel, which is the system component that provides SSL and TLS to applications. When FIPS mode is enabled, Schannel disallows SSL 2. FIPS standards. Applications such as web browsers that use Schannel then cannot connect to HTTPS web sites that dont use at least TLS 1. Note that the same results can be achieved without FIPS mode by configuring Schannel according to KB 2. Enabling FIPS mode also causes the. NET Framework to disallow the use of non validated algorithms. Microsoft advises not to use FIPS anymore as shown in the screenshot below http blogs. In our case this solved the issue with the error 6. Probably it was a combination of things, but this is certainly something to disable and try. Cause 5 Use the latest CU2 on CM1. R2 SP1 Always make sure to use the latest CUs as they include important fixes. You can download CU2 over here https support. The two most important fixes that may help to avoid error 6. CU2 for R2 SP1 are Applications will not install when you use them with a dynamic variable list in a task sequence if no SMB package share was defined for the content. This affects only installations that use a dynamic variable list. Other installation methods are unaffected. No Http location found Failed to download content for SMS package PRI0. Install Dynamic software action failed to resolve content for package. ID PRI0. 00. 80, program. ID Test. App. Error Code 0x. In a Configuration Manager environment in which multiple certificates are deployed to client computers, the client may select the wrong certificate for use in management point communication. This occurs when one certificate is based on a version 2 template and one is based on version 3. The client will select the certificate that has the longest validity period. This may be the version 3 certificate, and this certificate may not be currently supported by Configuration Manager. Errors that resemble the following are recorded in the Client. IDManager. Startup. Reg. Task Executing registration task synchronously. Reg. Task Failed to create registration request body. Error 0x. 80. 09. Hope it Helps ,Kenny Buntinx. MVP Enterprise Mobility. Clear the Windows Update Reboot Flag. This will help with the reset and remediation of a failed Windows Update. This is not for a update that failed to install. This is for a successful update that failed to remove the Reboot flags. This will forcefully remove the Reboot Pending windows update notice. Recently, several computers I manage had a fouled windows update that failed to clear the Windows Update reboot pending flag. The updates were installed and no updates were available. Whenever the PC was turned on Windows Update would ask for a reboot and would do so throughout the course of the day. This caused headache for the end users and myself a lot of pain until I found the solution. Please note that this is for a particular case and is not suitable in all cases. This will make changes to Windows Registry and Windows System Files to remove stuck Windows Update Reboot flags. This could even be scripted for an RMM platform using a batch file. Stop the Windows Update service From the Windows start, search for Services Shown in the image is Windows 1. In windows 7, click run and type services. Delete Registry keys Scroll down to the bottom and find Windows Update. Right Click and select Stop. Now delete some Windows Update registry keys, again search for regedit in Win. Drill down to the following Key in Regedit. HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrent. VersionWindows. UpdateAuto UpdateReboot. Red Alert 2 Yuri S Revenge No Cd Crack. Required Delete the Reboot. Required key in its entirety, Windows Update will re create it as needed. Close Regedit as it is no longer needed. Delete XML Files Open Explorer and browse to C WindowsWin. SXS There will be lots of folders in here, ignore them. Find two files called Reboot. XML and Pending. XML. One or both files may exist. They are easily found by sorting by File Type and scrolling to the top or bottom. Change Ownership Right click on the Reboot. XMLPending. XML file and go to Properties. Select the Security tab. Then Click Advanced. A New Windows will open, select Change Ownership. On the Select User dialog box, type the current username into the box, and click Check Names. The Account name should be underlined showing that a correct user has been selected. A box may pop up showing a list of matching users, select the current user account from the list. Click ApplyOK to all open dialog boxes. Change Permissions Right click on the Reboot. XMLPending. XML file and go to Properties. Then hit the Security tab. Click the Edit button the change permissions. Select Add, the Select User Dialog box will pop up. Type in the user Everyone click Check Names then OK. Select the Everyone user and check the box for Full Control ApplyOK out of all dialog boxes. Delete File Right click on the Reboot. XMLPending. XML files and Delete it. Reboot the PC to verify the reboot notification plague is gone.