

RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence. The smsts.log file reveals the following.įailed to get client identity (80072ee7).įailed to get time information from MP: An error occurred while retrieving policy for this computer (0x80004005).įor more information, contact your system administrator or helpdesk operator. For more information, please contact your system administrator or helpdesk operator. An error occurred while retrieving policy for this computer (0x80004005). Task Sequence fails with the following error message.

So here is the issue and it’s description. This issue was observed on one of the VM’s. In my case during the OSD the task sequence failed at the very initial step. Therefore you must examine the smsts.log file to find out the actual issue.

Which means there could be more than one solution for this error. Before you read further, I want to tell you that error 0x80004005 is a generic error. This post provides solution to SCCM task sequence error 0x80004005 while retrieving policy.
