My system is 4 years old running on the mobile Sandy Bridge chipset and I can't run anything newer than 12.x as 13.x and 14.x installers would say my chipset is not supported. If you're using version 10, it means you're on a older chipset that is not supported in the other versions. none with gui.Īlso I misstated the executable name above. they may have obfuscated it as when I websearch that version, all I see on the intel site is the barebone driver packaging. some assembly of that vintage had the full GUI and I'm beginning to think that was THE only one ever released. leaving such a bomb in the hands of a non-technical user is an errorįor anyone reading this now or henceforth the specific package version was 10.
#Intel raid controller driver windows 10 update
again unfortunately: once one loads a combination, one cannot safely prevent windows 10 update from overwriting your hard work. I found some of the best results to be had by using generic MS provided drivers.
#Intel raid controller driver windows 10 drivers
some 'windows 10 approved' drivers loadable via windows update are downright dangerous. still a lot of background traffic and the behavior of the gui is the same.Įditorial comment: on other windows 10 installs with varying success, it appears that merely "update to the latest" is not good advice. It is really difficult to check all the drivers, but I updated to the "official" only windows 10 drivers that intel posts. System runs, does what you want it do, but I have no idea what the integrity of the mirroring is since the errant upgrade. I noticed on another forum some fishing about for a driver that works, of whatever vintage. If I could figure out where I originally got that zip or msi or exe I think it would probably reinstall and work.Īside from that, many report ill-behaved results under windows 10 with the latest Intel drivers. The tray icon loads and looks normal until you actually try to DO something with the app, which invokes the GUI which hangs, bails, and impressively leaves NO ERROR in the windows event logs. I tried the windows 10 compatibility tools but nothing worked which didnt surprise me. its a normal looking application with a few subfolders, dating back a couple years, around 20MB worth of files. To the GUI, the Programs folder shows the app plainly.
Likely will have to start from zero and rebuild the whole thing. There ain't THAT much data on the system so I suspect the RAID driver may be giving it trouble. I kicked off a rollback this morning to Windows 7 and its been "restarting" since. I'll get on that Speccy assuming that system returns from its 'dark side of the moon'.
0 kommentar(er)
