Fix SCCM OSD Error 80190191 and Error 0x80070002

ByPrajwal Desai Hours

You deploy a SCCM task sequence and it fails with error 0x80070002. However the smsts.log file shows error 80190191. We know that 0x80070002 is a generic error and there can be multiple reasons for this error. While you see a generic error code, you cannot conclude anything here. You need to examine the smsts.log file to understand at what step the task sequence actually failed and the reason for it.

Last week one of the user contacted me about this error. He mentioned that the task sequence failed at Apply Operating System step. The task sequence failed with error code 0x80070002. The first thing that I suggested him is to check the smsts.log and ensure the network access account is configured.

In this post I will provide a solution for SCCM OSD error 80190191. If the solution doesn’t work for you, do mention in the comments section.

What is Network Access Account ?

The Network Access account is used only for accessing the content and not for running the task sequence. This account should have the minimum appropriate permissions on operating system deployment content it needs to access. This account is important because the computer receiving the operating system does not have a security context it can use to access content on the network.

To Configure the Network Access Account in SCCM

  • Launch Configuration Manager console.
  • Click Administration > Overview > Site Configuration.
  • Click Sites, on the top ribbon click Configure Site Components and then click Software Distribution.
  • Under Software Distribution Component Properties, click Network Access Account.
  • Select Specify the account that accesses network locations. Specify network access account.

Here is a video tutorial to create network access account in SCCM.

Reasons for SCCM OSD Error 80190191

Typically an error 80190191 occurs if any of the below conditions are true.

SCCM OSD Error 80190191 and 0x80070002Here is the snippet of smsts.log file.

401 - Unsuccessful with anonymous access. Retrying with context credentials.
Using thread token for request
401 - Unsuccessful with context credentials. Retrying with supplied credentials.
Network access account credentials are not supplied or invalid.
401 - Unsuccessful on all retries.
SendResourceRequest failed. 80190191
SendResourceRequest(pCertContext), HRESULT=80190191
Download failed. 80190191.
DownloadContentAndVerifyHash failed. 80070002.
Failed to run the action: Apply Operating System. The system cannot find the file specified. (Error: 80070002; Source: Windows)

Most of all, you see SCCM OSD error 80190191 because the network access account isn’t configured correctly. If you are not sure about that account, you may remove it and create a new account and add it.

In very rare case, you might need to verify the second reason for this error. If you see Download failed error 80190191 in smsts.log file, it could be due to Windows Authentication missing on the server. In such cases you must examine the IIS logfiles and double check if IIS is configured as per the actual requirements. Install the missing components on the distribution point server and the error should not appear again.

Avatar photo

Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.

7 Comments

  1. Just….thank you. You’re my SCCM hero.

  2. I have the same behaviour on surface devices when we start the Task sequence out of the current installed os.
    10 Apps install without problems and then “error”. On Dell devices it works without interruption.

  3. I have to concur that a working some machines and not other. Also, On the same machine. I have the issue where it downloads 6 files and then fails on the 7 file. This happens to use on a bunch of different packages. All we have been able to do is run the TS again and hope it completes.

  4. Amazing troubleshooting post, thank you Prajwal..

  5. If the error comes on 1 system only and rest working fine

    1. I don’t think there can be error on only one machine. Check your smsts.log file and verify if there is any other error code apart from one mentioned by Prajwal Desai

      1. There is, witness on 1 or 2 PCs out of thousands. Don’t want to delete CM object just of yet as doing further troubleshooting but not obvious why only 2 PCs fail consitently (and PCs built previously OK).

Comments are closed.