My optane chip is installed in the m.2 slot and is recognized by the windows device manager as some sort of hard disk. When I run the optane setup it says i must have a intel chipset 200 or higher and then errors out.
I checked the log report and there are two errors. One error is the cpu ID is not recognized and the PCH is not recognized. The windows device manager recognizes my cpu as an 8th generation processor.
My IDE SATA/ATAPI Controller under Device Manager is the "Standard SATA AHCI Controller". Should this be an Intel driver vs Microsoft? If so, none of the Intel chipset driver installation programs work - I've tried them all.
I've also had intel folks remotely use my computer to figure out what's wrong - hitting the same brick walls.
Any guidance would be great. I'm about to return the optane memory and just buy a Samsung SSD.
(Intel Customer Support - Case #: 03928853)
- I affray that you have to wait, till you will be able to enable your Optane memory on your NUC. To enable this future you have to install an Intel driver for Optane memory. However this driver is missing for a while from the Intel Download Site: https://downloadcenter.intel.com/product/126145/Intel-NUC-8-Home-a-Mini-PC-with-Windows-10-NUC8i3CYS... . This is because it was temporary removed for a maintenance: https://downloadcenter.intel.com/download/28058/Intel-Rapid-Storage-Technology-RAID-for-Intel-NUC-Ki...
- Any way, once the driver will be available again for download, install it and use the following guide to enable Optane memory on your NUC: https://www.intel.com/content/www/us/en/support/articles/000024061/mini-pcs/intel-nuc-kits.html
Hope this helps
Yes, it is through softpedia.
Intel NUC8i3CYSM Mini PC RST Driver 18.104.22.1687 for Windows 10 64-bit
The zipfile will have a few folders. You can go straight to optane folder and run the setup program. The setup takes about 15 min with install, resets, formatting/ enabling. But well worth it. My windows 10 loading time decreased by 62 seconds.
Literally had the same problem and literally solved it the same way.
Is there an Intel rep on hand that has insight into what is wrong with these drivers? If its a corner case I will likely just leave the one I found online but if its a legit issue, I would like to know and update when the time comes.