mdt missing iastorafs.sys 0xc0000098

Eaven HUANG 2,166 Reputation points
2023-01-18T09:52:37.2866667+00:00

Dear Experts,

I'm following this link [https://www.deploymentresearch.com/mdt-2013-lite-touch-driver-management/ ](https://www.deploymentresearch.com/mdt-2013-lite-touch-driver-management/"Link: https://www.deploymentresearch.com/mdt-2013-lite-touch-driver-management/")to set up total control method for our MDT. However I can't figure out what has gone wrong. Here are what I've done in our production:

  1. Deletted all the existing imported drivers from Out Of Box Driver, completely regenerated the DS image
  2. Created WinPE 10x64 folder in Out of Box Drivers under DS
  3. Import WinPE Driver Packs from DELL and HP official pages (I imported the entire package after they were extracted locally)
  4. Set up Selection Profile for Win 10.0X64 
  5. Selected this Selection Profile in DS Windows PE x64 section, set the size from 32 to 128
  6. Created new TS then set new DriverGroup with %Make%%Model% and set the default one to Nothing and use everything from Selection Profile
  7. Added new generated boot image into WDS, boot the client machine but still continue receiving the missing iastora.sys issue
  8. I manually deleted the folders in DS\Boot, let MDT to regenerate a new one from empty, tried with the computer again, failed with same error
  9. In WDS, I also set TFPT to 4095 and uncheck the option of extension...
  10. I knew from internet that HP comes with default AHCI, but not RAID optioin. I even changed our Dell PC from AHCI to RAID but no difference

It seems to me that MDT/WDS didn't really load the correct WinPE driver from my selection profile, I also noticed that we have quite a number of different versions of drivers after importing them from HP/DELL, what that be the cause? I'm still not figuring out how did you experts import the WINPE drivers into MDT, what exactly is needed in WINPE selection profile folder (OOBD)

Anyone can help with this? I'm completely lost here after spending over 2 weeks googling around and repeating generating new images.

I'm attaching the screenshots in my env for your further reference and any help is really appreciated.01

02

03

04

05

06

07

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
904 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. CherryZhang-MSFT 6,491 Reputation points
    2023-01-19T05:49:37.5033333+00:00

    Hi @Eaven Huang,

    To narrow down the problem, we need more information.

    1, Are you deploying operating systems for multiple PC models? Why you want to customize the Windows PE drivers? Can these PCs successfully install the operating system before you customize the Windows PE driver?

    2, As mentioned in the article your provided, for the boot image you need at Nic and Storage drivers at minimum. Have you experienced the problem during the installation of the operating system that require you must import the drivers manually? If not, I will do not recommend it. And if it is not necessary, I recommend that you select only the Nic and Storage drivers as showing the following screenshot:
    1

    3, If you must modify the Windows PE driver, please make sure it is appropriate for your computer model.

    4, Besides, I recommended that you create a new Deployment Share and do not modify anything about Windows PE. Then regenerate the boot image and import to the WDS to check if the error also appears?

    I will do more research; I will be sharing for you if I have any progress.

    Looking forward to your feedback.

    Best regards

    Cherry

     


  2. young wang 0 Reputation points
    2023-11-20T09:34:27.3333333+00:00

    any updates?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.