@theopenem_admin I figured it out. I had to rebuild my bootable ISO file with the new HD drivers added to the WinPE iso. Once I did this it worked fine. I have learned with each new piece of hardware we introduce into our network, I usually just go through these steps out of habit. 
@theopenem_admin I updated the BIOS per your request. The same problem is happening. It gets to 5% very slowly and then fails with the following error.
I'm having problems imaging to a newly installed SSD into an older Dell Optiplex 3050. I am able to get the imaging process started but it is VERY slow and it fails when it gets to 7%. The following is what I see in the applog on my server.
WinPE Version:
10.0.19041.0
System Architecture:
@{OSArchitecture=64-bit}
EFI Enabled / Secure Boot Disabled
** Looking For Active Task For .93BTXK2.4C4C4544-0033-4210-8054-B9C04F584B32 **
{"computerId":"false","task":"ond","taskId":null,"computerName":null}
...... This Computer Was Not Found
** Looking For Active Task For 50:9A:4C:58:B4:69.93BTXK2.4C4C4544-0033-4210-8054-B9C04F584B32 **
{"computerId":"false","task":"ond","taskId":null,"computerName":null}
...... This Computer Was Not Found
** Looking For Active Task For .93BTXK2.4C4C4544-0033-4210-8054-B9C04F584B32 **
{"computerId":"false","task":"ond","taskId":null,"computerName":null}
...... This Computer Was Not Found
** Looking For Active Task For **
{"Message":"An error has occurred."}
...... This Computer Was Not Found
** Looking For Active Task For 50:9A:4C:58:B4:69 **
{"computerId":"false","task":"ond","taskId":null,"computerName":null}
...... This Computer Was Not Found
** Looking For Active Task For **
{"Message":"An error has occurred."}
...... This Computer Was Not Found
** Using On Demand Mode **
** Looking For Model Match Task For OptiPlex 3050 **
This Computer Is Not Registered. No Active Web Tasks Were Found For This Computer. Starting Registration.
No Active Web Tasks Were Found For This Computer. Starting On Demand Imaging.
image_name=Win10v21h2_base
profile_id=43
pre_scripts=""
before_file_scripts=""
after_file_scripts=""
file_copy=False
sysprep_tags=""
web_cancel=true
task_completed_action="Reboot"
change_computer_name=true
skip_expand_volumes=true
fix_bcd=true
randomize_guids=true
skip_nvram=true
fix_bootloader=true
partition_method=dynamic
image_server="http://10.1.80.86:8888/clientimaging/"
computer_id=-147885
...... Success
** Looking For Hard Drive(s) **
** Displaying Available Devices **
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
0 NVMe Samsu... 0025_3855_2190_511A. Healthy Online 465.76 GB GPT
1 USB 2.0 Fl... 1 Healthy Online 3.75 GB GPT
...... Found 1 Drives
** Displaying Current Partition Table On 0
DiskPath: \?\scsi#disk&ven_nvme&prod_samsung_ssd_970#4&3714eef5&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
PartitionNumber DriveLetter Offset Size Type
1 1048576 260 MB System
2 273678336 16 MB Reserved
3 290455552 459.64 GB Basic
4 493820575744 500 MB Recovery
** Processing Hard Drive 0
Get hd_schema: profileId=43&clientHdNumber=0&newHdSize=500107862016&schemaHds=&clientLbs=0
{"BootPartition":"","Guid":"{bdf66dde-648d-4143-9825-1b696c98afb1}","IsValid":"true","Message":null,"PartitionType":"GPT","PhysicalPartitionCount":4,"PhysicalPartitions":[{"Compression":null,"EfiBootLoader":"","FileSystem":"FAT32","Guid":"{73a0ce8c-e726-4272-b802-70acc2652c0e}","ImageType":null,"Number":"1","PartcloneFileSystem":null,"Prefix":null,"Type":"System","Uuid":"","VolumeGroup":null},{"Compression":null,"EfiBootLoader":"","FileSystem":"","Guid":"{619233a9-f901-4639-9604-26ec6b9c485d}","ImageType":null,"Number":"2","PartcloneFileSystem":null,"Prefix":null,"Type":"Reserved","Uuid":"","VolumeGroup":null},{"Compression":null,"EfiBootLoader":"","FileSystem":"NTFS","Guid":"{90ce1fb8-a16d-49ef-8c41-74d27bf85552}","ImageType":null,"Number":"3","PartcloneFileSystem":null,"Prefix":null,"Type":"Basic","Uuid":"","VolumeGroup":null},{"Compression":null,"EfiBootLoader":"","FileSystem":"NTFS","Guid":"{1415df87-899c-4c69-9e23-68628a442f46}","ImageType":null,"Number":"4","PartcloneFileSystem":null,"Prefix":null,"Type":"Recovery","Uuid":"","VolumeGroup":null}],"SchemaHdNumber":0,"UsesLvm":"false"}
...... HD Meets The Minimum Sized Required
imageProfileId=43&hdToGet=0&newHDSize=500107862016&clientHD=0&taskType=deploy&partitionPrefix=&lbs=512 http://10.1.80.86:8888/clientimaging/GetPartLayout
** Partition Creation Script **
New-Partition 0 -GptType '{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}' -Size 260MB 2>&1 >> $clientLog
New-Partition 0 -GptType '{e3c9e316-0b5c-4db8-817d-f92df00215ae}' -Size 16MB 2>&1 >> $clientLog
New-Partition 0 -GptType '{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}' -Size 470667MB | Format-Volume -FileSystem NTFS 2>&1 >> $clientLog
New-Partition 0 -GptType '{de94bba4-06d1-4d40-a16a-bfd50179d6ac}' -Size 500MB | Format-Volume -FileSystem NTFS -NewFileSystemLabel WindowsRE 2>&1 >> $clientLog
DiskPath: \?\scsi#disk&ven_nvme&prod_samsung_ssd_970#4&3714eef5&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
PartitionNumber DriveLetter Offset Size Type
1 1048576 260 MB System
DiskPath: \?\scsi#disk&ven_nvme&prod_samsung_ssd_970#4&3714eef5&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
PartitionNumber DriveLetter Offset Size Type
2 273678336 16 MB Reserved
DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRemaining Size
NTFS Fixed Healthy OK 459.53 GB 459.64 GB
DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRemaining Size
WindowsRE NTFS Fixed Healthy OK 486.07 MB 500 MB
Microsoft DiskPart version 10.0.19041.1
Copyright (C) Microsoft Corporation.
On computer: MININT-N17Q0JQ
DISKPART>
Disk 0 is now the selected disk.
DISKPART>
Partition 1 is now the selected partition.
DISKPART>
0 percent completed
100 percent completed
DiskPart successfully formatted the volume.
DISKPART>
** New Partition Table Is **
DiskPath: \?\scsi#disk&ven_nvme&prod_samsung_ssd_970#4&3714eef5&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
PartitionNumber DriveLetter Offset Size Type
1 Q 1048576 260 MB System
2 273678336 16 MB Reserved
3 290455552 459.64 GB Basic
4 493820575744 500 MB Recovery
@{Compression=; EfiBootLoader=; FileSystem=FAT32; Guid={73a0ce8c-e726-4272-b802-70acc2652c0e}; ImageType=; Number=1; PartcloneFileSystem=; Prefix=; Type=System; Uuid=; VolumeGroup=}
@{Compression=; EfiBootLoader=; FileSystem=; Guid={619233a9-f901-4639-9604-26ec6b9c485d}; ImageType=; Number=2; PartcloneFileSystem=; Prefix=; Type=Reserved; Uuid=; VolumeGroup=}
@{Compression=; EfiBootLoader=; FileSystem=NTFS; Guid={90ce1fb8-a16d-49ef-8c41-74d27bf85552}; ImageType=; Number=3; PartcloneFileSystem=; Prefix=; Type=Basic; Uuid=; VolumeGroup=}
** Starting Image Download For Hard Drive 0 Partition 3
Set-Partition : The requested access path is already in use.
Activity ID: {ee9b46fe-cca6-4635-9ec2-fbb1e4b7ec43}
At X:\wie_deploy.ps1:182 char:5
Set-Partition -DiskNumber $($hardDrive.Number) -PartitionNumber $ ...
CategoryInfo : InvalidArgument: (StorageWMI:ROOT/Microsoft/..._StorageCmdlets) [Set-Partition], CimExce
ption
curl.exe -sSk -H Authorization:MkNFRDBFREQ0MEVBNDJCRDlDM0I4NkUxMjk1MUVCNDZCQjAzNjYzREEwRkM0NzM3OTlGOTU4OTkyNkI2QkIwNw== --data "profileId=43&hdNumber=0&fileName=part3.winpe.wim" http://10.1.80.86:8888/clientimaging/GetImagingFile | wimapply - 1 
[WARNING] Ignoring named data streams of 17 files
[WARNING] Ignoring FILE_ATTRIBUTE_COMPRESSED of 15 files
[WARNING] Ignoring FILE_ATTRIBUTE_SPARSE_FILE of 10 files
[WARNING] Extracting 34150 hard links as independent files
[WARNING] Ignoring reparse data of 54 files
[WARNING] Ignoring Windows NT security descriptors of 419186 files
[WARNING] Ignoring extended attributes of 20370 files
[WARNING] Ignoring object IDs of 26 files
[WARNING] Ignoring DOS names of 295264 files
[ERROR] Can't create directory "C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1586.1.7\amd64_microsoft-windows-t..ices-rdpsounddriver_31bf3856ad364e35_10.0.19041.746_none_18c2980b58d44ec1" (status=c00002ea): The directory or file cannot be created
ERROR: Exiting with error code 37:
Failed to create a directory.
** Making System Bootable **
Failure when attempting to copy boot files.
@{Compression=; EfiBootLoader=; FileSystem=NTFS; Guid={1415df87-899c-4c69-9e23-68628a442f46}; ImageType=; Number=4; PartcloneFileSystem=; Prefix=; Type=Recovery; Uuid=; VolumeGroup=}
** Closing Active Task **
@theopenem_admin What is involved in that? Did that suggestion work for the other guy?
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9152 --interface 10.1.80.86 --file e:\toems_local_storage\images\Windows11_v1\hd0\part1.winpe.wim
10-18-21 11:29 Starting Upload Session Windows11_v1 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9154 --interface 10.1.80.86 --file e:\toems_local_storage\images\Windows11_v1\hd0\part3.winpe.wim
10-19-21 11:48 Starting Upload Session Windows11_v2_withOffice2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9156 --interface 10.1.80.86 --file e:\toems_local_storage\images\Windows11_v2_withOffice2019\hd0\part1.winpe.wim
10-19-21 11:48 Starting Upload Session Windows11_v2_withOffice2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9158 --interface 10.1.80.86 --file e:\toems_local_storage\images\Windows11_v2_withOffice2019\hd0\part2.winpe.wim
10-19-21 11:48 Starting Upload Session Windows11_v2_withOffice2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9160 --interface 10.1.80.86 --file e:\toems_local_storage\images\Windows11_v2_withOffice2019\hd0\part4.winpe.wim
03-09-22 10:22 Starting Upload Session Win10_21h2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9162 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2\hd0\part1.winpe.wim
03-09-22 10:22 Starting Upload Session Win10_21h2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9164 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2\hd0\part2.winpe.wim
03-09-22 10:23 Starting Upload Session Win10_21h2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9166 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2\hd0\part4.winpe.wim
03-09-22 11:51 Starting Upload Session Win10_21H2_with_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9168 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21H2_with_Office2019\hd0\part1.winpe.wim
03-09-22 11:51 Starting Upload Session Win10_21H2_with_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9170 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21H2_with_Office2019\hd0\part2.winpe.wim
03-09-22 11:51 Starting Upload Session Win10_21H2_with_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9172 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21H2_with_Office2019\hd0\part4.winpe.wim
03-09-22 01:11 Starting Upload Session Win10_21h2_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9174 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2_Office2019\hd0\part1.winpe.wim
03-09-22 01:11 Starting Upload Session Win10_21h2_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9176 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2_Office2019\hd0\part2.winpe.wim
03-09-22 01:11 Starting Upload Session Win10_21h2_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9178 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2_Office2019\hd0\part4.winpe.wim
03-16-22 09:45 Starting Upload Session Win10_21h2_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9180 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2_Office2019\hd0\part1.winpe.wim
03-16-22 09:45 Starting Upload Session Win10_21h2_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9182 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2_Office2019\hd0\part2.winpe.wim
03-16-22 09:45 Starting Upload Session Win10_21h2_Office2019 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9184 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_21h2_Office2019\hd0\part4.winpe.wim
07-14-22 01:28 Starting Upload Session Win11_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9186 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win11_OS_Only\hd0\part1.winpe.wim
07-14-22 01:29 Starting Upload Session Win11_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9188 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win11_OS_Only\hd0\part3.winpe.wim
07-14-22 01:45 Starting Upload Session Win11_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9190 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win11_OS_Only\hd0\part4.winpe.wim
07-14-22 03:57 Starting Upload Session Win10_v21h2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9192 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_v21h2\hd0\part1.winpe.wim
07-14-22 03:58 Starting Upload Session Win10_v21h2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9194 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_v21h2\hd0\part3.winpe.wim
07-14-22 03:58 Starting Upload Session Win10_v21h2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9196 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_v21h2\hd0\part4.winpe.wim
07-14-22 04:04 Starting Upload Session Win10_v21h2_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9198 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_v21h2_OS_Only\hd0\part1.winpe.wim
07-14-22 04:05 Starting Upload Session Win10_v21h2_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9200 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_v21h2_OS_Only\hd0\part3.winpe.wim
07-14-22 04:05 Starting Upload Session Win10_v21h2_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9202 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10_v21h2_OS_Only\hd0\part4.winpe.wim
07-15-22 02:29 Starting Upload Session Win10v21H2_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9204 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10v21H2_OS_Only\hd0\part1.winpe.wim
07-15-22 02:30 Starting Upload Session Win10v21H2_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9206 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10v21H2_OS_Only\hd0\part3.winpe.wim
07-15-22 02:30 Starting Upload Session Win10v21H2_OS_Only With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9208 --interface 10.1.80.86 --file e:\toems_local_storage\images\Win10v21H2_OS_Only\hd0\part4.winpe.wim
07-18-22 01:51 Starting Upload Session TestImage With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9210 --interface 10.1.80.86 --file e:\toems_local_storage\images\TestImage\hd0\part1.winpe.wim
07-18-22 01:51 Starting Upload Session TestImage With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9212 --interface 10.1.80.86 --file e:\toems_local_storage\images\TestImage\hd0\part3.winpe.wim
07-18-22 01:51 Starting Upload Session TestImage With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9214 --interface 10.1.80.86 --file e:\toems_local_storage\images\TestImage\hd0\part4.winpe.wim
07-18-22 01:58 Starting Upload Session Testimage2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9216 --interface 10.1.80.86 --file e:\toems_local_storage\images\Testimage2\hd0\part1.winpe.wim
07-18-22 01:58 Starting Upload Session Testimage2 With The Following Command:
cmd.exe /c "C:\Program Files\Theopenem\Toec-API\private\apps\udp-receiver.exe" --portbase 9218 --interface 10.1.80.86 --file e:\toems_local_storage\images\Testimage2\hd0\part3.winpe.wim
I have gone so far as to try using the older ISO file from before I updated the server and now that does the same thing as the new ISO.
@theopenem_admin This is from my virtual machine. In the past I have used a VM to create a universal image. It has worked perfectly until this update to my server. I have my image ready to go. I boot from the new SuperISO i create with the drivers added to it and it only creates the 100m file. I see a lot of the same error from the post I shared with you.
I did find another post in the forums that is having the same issue I am having.
This post did not have a resolution from what I can tell. Did this user get around the issue?
@theopenem_admin I did. When I try to image now all it will do is create a 100M size image.