@Fernando

thanks for your reply

yeah i knew that all

what i am facing with is , no matter which version, from 10.x to 17.x i could get, the installer prompted platform not supported. and i have tried to install it with nodrv param, install the msi directly, install the drivers manually, but for some reasons, i observed that some of the registry entries couldnt be updated/added. also, the iastora.sys was still the v15 one and not replaced by the new installation. this is weird. simply speaking, there's no driver to handle the raid drives and bsod again if i put the disks back

edit i also tried the modded one here, it prompted me with a strange error "cannot write to power xxx" in the registry

if i don have a working copy (the backup version), i would probably give up. however, there's a working one on hand so i know it should work, but need some magic!


edit2 you can see the difference here with the key highlighted, one is empty and the other with sub keys (not talking about iaahcic specifcally, just as an example)

on the current system with non-working raid


on the backup system with working raid

yes, the images are for reference only, showing some registry enteries are missing

the v15 iastora.sys is located in system32, alongside with some other files with different versions, i believe it was the leftover from the raid 0 installed long time ago but removed mths before. i can see different versions of irst files inside system32 as well as in the registry.

under storage controllers, in the working system, it's 14.8.16.1063, while it is v15 on the non working system. note that the working system was built on the non working one. ie, i successfully turned it into a working system from v15

edit coz right now i am with the working system i can only capture the key which i have posted before for comparison. and you can see the differenece between the 2 systems's device manager in the 1st post

it is ok for me.

@johnson
I think your best option should be to do a fresh OS install. For me your PC is not clear.
On my side I never have to look at the W10 registry to manage RAID configurations.
Moreover migrating one system over one other , install and reinstall over and over drivers, modifying Registry, etc.. are source of lot and unexpected problems.

@100PIER

i agree with u and if u ask me i would give you the same suggestion. but for me it would be a disaster to reinstall the os coz there are a lot of tiny things i need to do including some registry hacks and settings. i think i will try a few times more in order to get the drivers working again first.i think i am almost there. this is due to my personality perhaps :D

thanks for your help once again

I understand that tuning a PC system does require lot of energy and time.
You have the opportunity in May to switch to W10 H1-2019 version v1903.

well, i have not been chasing for new version for a long time ago.... so i will stick with the current one for coming years

and btw, here is a good news . i just made it finally!!

sorry for the delay and i want to take this opportunity to summarize the problems i encountered for ppl who need help just in case

the main problem was, new drivers were not installed, or not installed properly, which led to (i will use iaStorA.sys as example):

1) file system
- the new driver, iaStorA.sys, was not copied to windows\system32\drivers\ to replace the existing one, although they might be added to the Windows\System32\DriverStore\FileRepository\ already

2) registry
- registry entries for the old drivers were still there and not overwritten by the new one
- new driver entries were not added or completely written, and some of the subkeys were missing
- due to the above errors, under device manager, the drivers for the raid storage controller could not be shown correctly or even no intel storage controller would be available for your raid

remember, always do a backup first

finally, thanks to @Fernando @100PIER for their help and valuable info. i learnt a lot here really

no, i will never delete any driver by myself normally. deleting the driver file itself wont help and can cause problem since they are registered

no, i didnt delete any entries before. as i shown you i had the files and registry entries
i bet the problems were due to a failed driver downgrade

I do observe by experience that Intel storage driver downgrade operation is sometimes a source of problems and a restore saved the life of the PC.