Let’s see how you can FIX SCCM Task Sequence Unable to find a volume Error Code 0x80070490. You might encounter a prompt error message while performing operating system deployment with SCCM Task Sequence. The error is often seen when you will perform the deployment in new machines.
The Task Sequence Error is generic, and the solution could be different based on the details you get into logs.
First of all, you will need to understand what is the meaning of the error code 0x80070490. You can try to use the method to translate SCCM Error Codes To Error Messages. The error code 0x80070490 translates to Element not found.
Examining the SMSTS log for task sequence failure issues is always recommended to help you understand the failure prompt. More you can explore SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide SMSTS.log.
Let’s look at the list of official Microsoft tools for reading the SCCM related log files. You can use all these SCCM log viewer tools to check different types of log files .log or .lo_ file extensions Top SCCM Log File Viewer Options for Admin.
- SCCM Deployment Failed to Resolve Task Sequence Dependencies 0X80040102
- FIX: SCCM TS environment is not initialized Error 0x80007002
- FIX: SCCM Task Sequence Failed to find a valid network adaptor
Issue Summary – SCCM Task Sequence Unable to find a volume Error Code 0x80070490
The Task Sequence is failing on formatting the disk. That you could have an issue with the partitioning or sometimes due to BitLocker encryption. This error occurs when attempting to run an operating system deployment task sequence.
In a step, it tried to copy the files to the local hard drive but could not find the path as the drive is in the RAW state.
Here are the highlights of the SCCM Task Sequence Unable to find a volume Error Code 0x80070490 from the SMSTS.log, Unable to find the system disk for this machine. Failed to prepare system partition for staging. Failed to stage WinPE –
Volume X:\ is not a fixed disk
Unable to find a volume that is suitable for staging the boot image. Element not found. (Error: 80070490; Source: Windows)
Failed to validate for boot image staging
StageBootImage() failed 0x80070490)
Failed to stage WinPE. Code(0x80070490)FIX – SCCM Task Sequence Unable to find a volume Error Code 0x80070490
To fix this issue, The drive needs to be formatted before continuing with the task sequence. Let’s follow the steps below to format the hard drive –
If you’re already in the error windows, the screen Task sequence has failed with the error code 0x80070490. Press F8 to launch the command prompt window or Restart the machine and boot with the same task sequence.
Important – Enable command support (F8) that is not recommended for production use. You can explore the available command prompt support option in Boot Image.
The diskpart command interpreter helps you manage your computer’s drives (disks, partitions, volumes, or virtual hard disks). Type the following commands in the command prompt –
Diskpart
List disk (Displays all the disks on the device)
Select disk 0
Clean (Wipes the disk)
Create partition primary (Creates windows partition)
Select partition 1
Format quick fs=NTFS (Format primary partition)
Assign letter C
ExitAnother FIX SCCM Task Sequence Unable to find a volume Error Code 0x80070490
Kevin suggested in the comments below that he found the solution to the problem. This was a BIOS setting issue. Dell Lattitude 7530 right out of the manufacturer’s packaging box.
- Items to change in BIOS settings:
Under BOOT CONFIGURATION, Disable Secure Boot
Under STORAGE, change SATA/NVME Operation from RAID to AHCI/NVMe.
Under PRE-BOOT BEHAVIOR, Fastboot should be set to Auto.
SCCM will then be able to see the storage device and be able to run the task sequences for images.
Disclaimer – The information provided on site is for general informational purposes only. All information on the site is provided in good faith, however, we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the website.
Once you are done with the above steps, Restart the target machine and reinitiate the task sequence deployment, It should continue without any errors.
Author
About Author -> Jitesh has over 5 years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10, Windows 11 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.
I found the solution to the problem. This was a BIOS setting issue. Dell Lattitude 7530 right out of manufacturers packaging box.
Items to change in BIOS settings:
Under BOOT CONFIGURATION, Disable Secure Boot
Under STORAGE, change SATA/NVME Operation from RAID to AHCI/NVMe.
Under PRE-BOOT BEAHAVIOR, Fastboot should be set to Auto.
SCCM will then be able to see the storage device and be able to run task sequence for image.
Hope this helps someone.
Hi Kevin,
Exactly this helped us get going with our new computers, now we can SCCM. Thanks 🙂
Thank you Kevin. This fixed my issue today I was having.
This is the way. This worked on a 5430 out of the box as well with the same error.
I am *SO* grateful for your posting this! You’ve been an amazing resource on our MEM journey and the Dell BIOS settings were exactly what we needed. We’re still rejoicing and want you to know that we value the time you spend putting this content out there.
Thank you, sir!
Thank You So much. It worked. It helped me a lot. Thank you for keeping my good image at my company lol
Thanks for support
Your Diskpart didnt Work for me
i Try this and work fine
diskpart
Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit
Thanks Kevin! Adjusting the same BIOS settings solved the problem on our new Dell OptiPlex 5000’s.
Hello Tstoner !
Thanks for your sharing and solution that work perfectly on my side each time I have this error code.
Enjoy your day
This got me going in the right direction. On the HP Z2 G9 you must uncheck the “Configure Storage Controller for VMD” in the BIOS under Advanced > System Options.
Thank you.
Hi
I’m having this problem but it is to to with bit locker. When I suspend bit locker the task sequence work.
Any idea please as why “Disable Bit locker step is not working?
Hello together I have new findings,
what can also lead to the problem if another device e.g. USB-Stick has taken the drive letter C in the SCCM TaskSequence. For this I have adapted my diskpart commands.
diskpart
select volume 0
remove letter=c
select volume 1
remove letter=c
select volume 2
remove letter=c
select volume 3
remove letter=c
select volume 4
remove letter=c
Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit
I had this issue with a Dell OptiPlex 7010, which I fixed by adding the ‘Intel RST VMD Controller 9A0B’ driver to the boot image. The Class is ‘SCSIAdapter’, which Config Mgr will question because it’s not Storage or Network, but I went ahead.
Hi this method is fonctional for me too
I tace to taank you so much
diskpart
Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit
Hello Everyone,
Is there a way to automate all the above Diskpart commands to run before the task sequence so that we need not worry about it every time we image a device?
Hello everyone,
I’m a bit new to the topic but in fact it would be nice to have one more opinion from your side regarding this topic.
I have seen the exact same error message for my PRODUCTION TS but this happened in the following scenario:
1) I have the PROD TS – configured with WinPE_1.0
2) I have a TEST TS created based on a COPY of the PROD TS – but configured with WinPE_1.2
The WinPE_1.2 was created based on the WinPE_1.0 and we added/imported some specific WinPE drivers to support a new Hw model that will be purchased. The WinPE drivers were downloaded from the vendor website and they are the official WinPE drivers released by the vendor, so no doubt about the drives.
Now when booting into PXE, I noticed that the WIM file that is loaded is the one from WinPE_1.2
Then the Task sequence wizard is opening, loading the policies and the list of these two available TS is displayed.
If I select and run the PROD TS configured as mentioned at point1 that uses WinPE_1.0 the deployment fails with the same error messages and the same information in the smsts.log file.
If I run the “COPY of the PROD TS” configured as mentioned at point 2 that uses the WinPE_1.2 the deployment goes further and it is completed successfully without issues.
So, to summarize, first we boot into PXE correctly and I noticed the wim file for WinPE_1.2 is loaded but then when running the TS from the TS wizard menu the task sequence that is configured to use a different WinPE then the one that was loaded when booting into PXE the TS cannot run and it fails.
As per my understanding once you have a new WinPE created that will be always loaded when booting into PXE.
I’m assuming this behavior is normal but I will appreciate a bit more context why this happens.
I guess there is a validation and since we booted in PXE using the wim file for WinPE_1.2 while the TS is configured to use the WinPE_1.0 that is NOT consistent and then it fails…?!?
I will really appreciate all your answers.
Thank you all!