Error code 2147942450

Hi,

We updated our SCCM-server to 2012 R2 SP1 so now it should be Windows 10 ready. Tried it, bootup works and install starts, however, during install drivers won’t be installed.

We got some error which points to WINPE. We have ADK 8.1, should/can we upgrade to 10 without impacting our current Windows 7 deployment (http://blogs.technet.com/b/yongrhee/archive/2015/08/11/download-windows-10-assessment-and-deployment-kit-adk.aspx
 mentions:  “The Windows Performance Toolkit (WPT better known as WPRUI/WPR/Xperf) that ships with Windows 10 ADK/SDK is not compatible with Windows 7 SP1 or Windows Server 2008 R2 SP1.  The stack (module!function) will
show up as ???!???.  Use the Windows 8.1 ADK/SDK instead.”

—the error—

The task sequence execution engine failed executing the action (W10x64) in the group (Windows 10) with the error code 2147942450

Action output: … rectory security

c:_smstasksequencepackagestrs02484b9d10a4f-7bb8-4520-8c41-bb867889bf1b is a directory. Setting directory security

c:_smstasksequencepackagestrs02484c9af2e40-a8d5-4aa8-8999-af88169782c2 is a directory. Setting directory security

c:_smstasksequencepackagestrs02484d5feabe7-c40a-4391-b90b-e90a2aa1b209 is a directory.

Setting directory security

c:_smstasksequencepackagestrs0248473bd6f73-ec33-493c-a4b9-809cade6c22bx64 is a directory. Setting directory security

C

Error: 50

To service this Windows image requires the latest version of the DISM. See http://go.microsoft.com/fwlink/?LinkId=293395 to find the latest version of DISM,

and http://go.microsoft.com/fwlink/?LinkId=293394 to learn how to install the latest version of DISM from the ADK on your computer.

The DISM log file can be found at C:_SMSTaskSequencePkgMgrTempdism.log

Dism failed with return code 50

Failed to add driver to driver store. Code 0x80070032

Failed to provision driver. Code 0x80070032. The operating system reported error 2147942450: The request is not supported.

—

Jan Hoedt

If you’re using a 12th Generation Dell server, disable the SD Card in the BIOS.  Keep reading for how I discovered this.

We recently received a handful of new Dell R720s and needed to lay down Windows Server 2008 x64. Got everything cabled, powered them up, PXE booted from our SCCM 2007 machine, it formatted the disks, and right when it went to deploy the OS, it failed with (taken from the SCCM Console, advertisement status):

The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942450
Action output: d-x64.xml”
Not a data image
ApplyOSRetry:
TSLaunchMode: PXE
OSDUseAlreadyDeployedImage: FALSE
Searching for next available volume:
Volume E: is a valid target.
Found volume E:!sSystemPart.empty(), HRESULT=80004005 (e:nts_sms_fresmsframeworktscorediskvolume.cpp,128)
Unable to locate a bootable volume. Attempting to make E: bootable.
volume.getDisk() == iBootDisk, HRESULT=80070032 (e:nts_sms_fresmsclientosdeploymentapplyosinstallcommon.cpp,680)
MakeVolumeBootable( pszVolume ), HRESULT=80070032 (e:nts_sms_fresmsclientosdeploymentapplyosinstallcommon.cpp,759)
ConfigureBootVolume(targetVolume), HRESULT=80070032 (e:nts_sms_fresmsclientosdeploymentapplyosapplyos.cpp,364)
System partition not set
Volume E: is not on the boot disk and can not be made bootable.
Failed to make volume E: bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system.
The request is not supported. (Error: 80070032; Source: Windows). The operating system reported error 2147942450: The request is not supported.

But what does that mean?

If you notice, there are all sorts of errors in there, but the main one to focus on is 80070032. After Googling this for a while, I read all sorts of posts, but almost all of them pointed do disk format issues.

I opened the smsts.log with SMS Trace and saw this:

‘System partition not set’ means no partition is set as bootable with an MBR, aka the ‘system’ partition.

‘Volume E: is not on the boot disk and can not be made bootable’  But why is it not, it’s the only physical disk?  Are you sure?  It’s all because of our little friend, Mr. SD Card.

Yeah? And now what?

At first glance, it looks like it’s having trouble working with the E drive, which seems totally logical, as that’s partition 0 on disk 0.

I ran through the typical steps of using diskpart to clean & partition the disk, everything looked fine. It was when I fat-fingered the format command that I discovered the issue. I had actually typed “format c: /q” and saw something about it already having a label and that it’s FAT or FAT32, one of the two, not NTFS, though, and we need NTFS.

After a quick check, the internal SD card was getting picked up as the C drive, and might actually be write-protected (I didn’t check).

I disabled it in the BIOS and BAM!!! OSD is now working.

@ventoy @todorvelichkov

I have some advice which can help some people. I’m on Windows 10 Pro and using Windows Defender antivirus.

I was getting the exact same ErrCode:5 in Ventoy’s log.txt which means «access denied».

I tried using Disk Management (Start-Run diskmgmt.msc) and deleting existing USB partitions but it didn’t work.

Then I had another idea…

I started PowerShell as Admin (Press Win+X and start Windows PowerShell (Admin)).

Next, I typed diskpart to open the Windows command line disk partitioning tool.

Then I used the following commands to list the disks, select the correct (USB) disk, run clean to erase EVERYTHING on that disk. IMPORTANT: You need to adjust these commands for your own system. It’s a good idea to list partition after selecting a disk, to be totally sure you got the correct disk!

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.
On computer: ...

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1863 GB  1024 KB        *
  Disk 1    Online         1907 GB      0 B        *
  Disk 2    Online         1907 GB  1024 KB        *
  Disk 3    Online         1907 GB  1024 KB        *
  Disk 4    Online           28 GB      0 B
  Disk 5    No Media           0 B      0 B

DISKPART> select disk 4

Disk 4 is now the selected disk.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
* Partition 1    Primary             28 GB      0 B

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> exit

Leaving DiskPart...

Now after cleaning the disk with diskpart, it’s basically «fresh» and not write-protected anymore.

All I had to do now was just install with Ventoy and voila it worked. I didn’t even have to disable Windows Defender or reboot the computer first or anything else. Ventoy’s installer just worked immediately after «cleaning» the disk with diskpart!