iastorafs.sys error after sysprep on windows 10 laptop running 1809

[casinokid26]

Hi,

iaStorAfs.sys file is missing, error code 0xc0000098​

I am getting iastorafs.sys error after sysprep on windows 10 laptop running 1809.

So I setup the laptop, actually when I set it up it has a M.2 NVME drive and I had to go into BIOS and change it off RST storage to the NVME option. Otherwise I got the iastorafs.sys error after installing windows. Cool, nice to know but after I got everything setup I copied everything to another NVME and ran sysprep with no unattend file and no special options.

Upon reboot it gave me the exact same iastorafs error, but thats wierd because it doesn't need the storage driver (or doesn't upon reboot after a fresh install).

My initial thoughts are that I need an unattend file to keep the drivers post sysprep but that doesn't make sense because it boots on a fresh install with the basic win10 drivers. Someone mentioned maybe check UEFI / secure boot settings. I'm pretty much at the point where I would sysprep it again so I'm ready to try it again on Monday (after a fresh capture of the image).

 

[DVDR_Dog]

Did your laptop have Win 10 when it was delivered new? I take it you are using a generic ISO and using Rufus to make these ISO bootable. There is some question about how Gen 11 Intel CPU and the RST drivers. Something to the effect that what Rufus' PE config loads the wrong (older version) of the RST driver and even if you patch the install, the old driver is still present alongside the newer version and may be loaded.
The easy way out is IF your laptop is a HP AND it came with Win 10, get a recovery image directly from HP. If not you are going to have to figure out the entire RST debacle and use a program that will allow you to make the ISO bootable and allow you to select only the proper RST or wait until Rufus is updated hopefully.

 

[casinokid26]

Did your laptop have Win 10 when it was delivered new? I take it you are using a generic ISO and using Rufus to make these ISO bootable. There is some question about how Gen 11 Intel CPU and the RST drivers. Something to the effect that what Rufus' PE config loads the wrong (older version) of the RST driver and even if you patch the install, the old driver is still present alongside the newer version and may be loaded.
The easy way out is IF your laptop is a HP AND it came with Win 10, get a recovery image directly from HP. If not you are going to have to figure out the entire RST debacle and use a program that will allow you to make the ISO bootable and allow you to select only the proper RST or wait until Rufus is updated hopefully.

Not a HP ( dude you got a Dell! ) but I did use rufus.

What if I just mount the iso and copy the contents to a usb is that bootable or what is the best non rufus tool? This is all googlable stuff but thanks for the tip on the rufus bug. Appreciated.

 

[DVDR_Dog]

Well that stuff you googled is valid. If Dell is supporting Win 10 on your system I would think they would post the fix, they are probably better at support than any others IMO.
So what is this mystery Dell you are having problems with? I have a bunch of Dells here and as work systems and I haven't encountered your problem. I'd like to figure out what's happening too.
Have you tired just using Microsoft's bootable image? I ask because Rufus seemed to be the common denominator with these RST drivers not being correct.

 

[casinokid26]

Well that stuff you googled is valid. If Dell is supporting Win 10 on your system I would think they would post the fix, they are probably better at support than any others IMO.
So what is this mystery Dell you are having problems with? I have a bunch of Dells here and as work systems and I haven't encountered your problem. I'd like to figure out what's happening too.
Have you tired just using Microsoft's bootable image? I ask because Rufus seemed to be the common denominator with these RST drivers not being correct.

Dell says this is beyond basic install stuff and wants you to pay per hour for this fix lol.

Another thing to point out is you get this exact same error post install and it is fixed by going into bios and switching from RST sata storage to M.2 NVME storage.

So if this was somehow caused by rufus I would need a fresh from a non rufus bootable. I'm going to try a few things like using an unattended file before I scrap the image.

This could all be part of the fun of booting on m2 nvme. I might the unattend file to make this happen.

 

[DVDR_Dog]

This could all be part of the fun of booting on m2 nvme. I might the unattend file to make this happen.

No I don't think so. I have 2 Dells at home and my work system, all Dells booting from m2 nvme drives with no problem. One thing, I don't believe I used a Rufus prepared image on any of the Dells I own.

 

[Ultimately 7]

WAY too much ASSUMPTION going on here...

The only time, in my experience that SYSPREP comes up, is when someone is trying to "Image" something.

But............... don't mind me... but I am remiss if I do not interject and SPELL OUT what I deem is Vague and Ambiguous INFO..... and how ANYONE can respond with clarity to such a vague and ambiguous post!

SYSPREP is ONLY for imaging and trying to make an OOBE image... yes?

"I am getting iastorafs.sys error after sysprep on windows 10 laptop running 1809."

This is simply not good enough for me, or ANYONE else to respond towards,,, simply because it has sevral meanings which are AQLL unique...