Task sequence fails to install applications on Windows 10 22H2 image. SCCM 2211 Error -2147467259 (0x80004005)

Question

After creating a new BC of windows 10 22H2 (which by the way completes succesfully without any errors) and implementing it in a 2nd task sequence the applications doesn't want to install with the above error. When going back to Windows 10 21h2 image, insalling applications work and everything. See log:

2023-10-17_13-58-41.png

2023-10-17_13-52-33.png

2023-10-17_13-55-59.png

At first the windows 10 22H2 came up with an error: Why did my pc restart, but this has been solved by adding 2 lines at the .xml file:

<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>

I can't seem to figure out why 22h2 image doesn't work, especially since the BC completes without any errors or warnings.

Answer 1

Hi,

PsExec is a command-line tool that allows you to execute processes under the SYSTEM account. You can do a test manual install the application on Windows 10 22H2.

Keep in mind that using PsExec in this way is for testing and troubleshooting purposes. Be cautious, as running commands under the SYSTEM account can have elevated privileges and should be done responsibly. After your test, you should still resolve the issue within your SCCM task sequence to ensure successful, automated application installations.

BTW: Which Forepoint component would you like to install?

For Windows:
Forcepoint DLP Endpoint:(Requires Forcepoint DLP v8.8.x or later)	23.04.5642
Forcepoint Web Security Proxy Connect Endpoint:(Requires Forcepoint Web Security v8.5.3 or later)	23.04.5642
Forcepoint Web Security Direct Connect Endpoint:(Requires Forcepoint Web Security v8.5.3 or later)	23.04.5642
Remote Filtering Client:(Requires Forcepoint URL Filtering v8.5.3 or later)	23.04.5642
Forcepoint Endpoint Context Agent:(Requires Forcepoint Next Generation Firewall v6.7–v6.10)	23.04.5642
Forcepoint CASB Endpoint:(Requires a Forcepoint CASB license)	23.04.5642

Answer 2

For testing purpose, can we set continue on error to true for this problematic task? And share the log file with sensitive information filtered.

To double confirm if this relates to OS image, can we use the original install.wim extracted from the .iso file, other than the BC one. In addition, could you share more details about BC the 22H2 image?

If possible, please share the screenshots when executing psexec -i -s cmd.exe

How to: become the LOCAL SYSTEM account with PsExec

Answer 3

Hi,

To narrow down the problem. We could try to temporarily disable the following suspicious tasks in build and capture task sequence and recapture the image.