I have an open ticket with Intel-I've posted it here-extremely frustrated Windows 10 user

%3CLINGO-SUB%20id%3D%22lingo-sub-1662425%22%20slang%3D%22en-US%22%3EI%20have%20an%20open%20ticket%20with%20Intel-I've%20posted%20it%20here-extremely%20frustrated%20Windows%2010%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1662425%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20Intel%20people%2C%20I%20am%20also%20going%20to%20post%20this%20directly%20into%20the%20Microsoft%20Community%20Forums%20-%20just%20so%20you%20know.%3C%2FP%3E%3CP%3EI%20have%20been%20using%2Fconfiguring%2Fmaintaining%20and%20troubleshooting%20Winblows%2C%20Linux%20and%20Unix%20Operating%20Systems%20since%20Windows%2095%20was%20but%20a%20baby.%20I%20have%20NEVER%20in%20my%2037%20years%20of%20IT%20seen%20something%20as%20crude%2C%20unstable%20and%20NOT%20ready%20for%20public%20release%20as%20the%20%22feature%20update%22%20to%20Windows%2010%202004.%3C%2FP%3E%3CP%3EIt%20is%2C%20without%20a%20doubt%20the%20MOST%20pathetic%2C%20beta%20release%20of%20any%20Operating%20System%2C%20software%20or%20driver%20that's%20been%20release%20in%20all%20that%20time.%20Since%20the%20release%20of%20Winblows%2010%20I%20have%20implemented%20no%20less%20than%204%20backup%20locations%2C%20one%20of%20which%20is%20offline%2C%20simply%20because%20MS%20can%20no%20longer%20be%20trusted%20to%20delivery%20a%20clock%20software%20much%20less%20a%20whole%20Operating%20System.%3C%2FP%3E%3CP%3EI%20set%20my%20feature%20updates%20to%20365%20days%20for%20a%20reason.%20This%20time%20I%20figured%20-%20it's%20been%20four%20months%2C%20surely%20MS%20has%20worked%20out%20all%20the%20beta%20bugs%20of%20their%20%22Public%20Release%22%20by%20now.%20I%20was%20TOTALLY%20wrong%20and%20will%20not%20do%20this%20again.%3C%2FP%3E%3CP%3EI%20don't%20really%20blame%20MS%20for%20this%2C%20I%20know%20they're%20mostly%20incompetent%20when%20it%20comes%20to%20feature%20updates%2C%20I%20blame%20myself%20for%20breaking%20the%20golden%20365%20day%20rule.%3C%2FP%3E%3CP%3EI%20am%20beginning%20to%20hate%20Microsoft%20with%20a%20passion%20normally%20reserved%20for%20love%20making!!%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3EOK%20-%20With%20the%20above%20frustration%20out%20of%20the%20way%2C%20lets%20move%20back%20to%20a%20more%20professional%20attitude.%3C%2FP%3E%3CP%3EI%20am%20using%20Intel%20Memory%20and%20Storage%20Tool%20ver.%201.2.79%20(most%20recent%20as%20of%20today).%3CBR%20%2F%3EI%20cannot%20optimize%20my%20665p%20NvME%20drive%2C%20all%20other%20functions%20SEEM%20to%20be%20working%20as%20expected%3CBR%20%2F%3EI%20have%20installed%20Windows%202004%20Build%20-%2019041.508%3CBR%20%2F%3EWhen%20I%20check%20the%20driver%20in%20use%20on%20the%20NvME%20it%20states%3A%3CBR%20%2F%3EProvider%3A%20Microsoft%3CBR%20%2F%3EDriver%20Date%3A%202006-06-21%20(a%2014%20year%20old%20driver%20-%20ffs%20MS%20has%20gone%20absolutely%20crazy)%3CBR%20%2F%3EDriver%20Version%3A%2010.0.19041.1%3CBR%20%2F%3EDigital%20Signer%3A%20Microsoft%20Windows%3C%2FP%3E%3CP%3EThis%20is%20obviously%20NOT%20ideal%20and%20I%20am%20trying%20to%20install%20the%20actual%20Intel%20driver%20for%20my%20NvME%20found%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdownloadcenter.intel.com%2Fdownload%2F29172%2FClient-NVMe-Microsoft-Windows-Drivers-for-Intel-SSDs%3Fproduct%3D83424%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdownloadcenter.intel.com%2Fdownload%2F29172%2FClient-NVMe-Microsoft-Windows-Drivers-for-Intel-SSDs%3Fproduct%3D83424%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20have%20tried%20a%20manual%20install%20via%3A%20Client-64bit_f6flpy.zip%20-%20which%20resulted%20in%20Winblows%20telling%20the%20BEST%20driver%20is%20already%20installed.%3CBR%20%2F%3EI%20have%20tried%20installing%20via%3A%20Setup_NVME.exe%20-%20which%20resulted%20in%20your%20install%20program%20telling%20no%20supported%20devices%20were%20found%3C%2FP%3E%3CP%3EI%20have%20searched%20using%20Windows%20Update%20and%20no%20new%20drivers%20found%20because%20apparently%20that%20driver%20from%202006%20is%20the%20BEST%20one%20to%20be%20used.%3C%2FP%3E%3CP%3EDear%20Intel%20tech%20support%2C%20please%20help%20me%20get%20the%20proer%20driver%20for%20your%20wi%3Donderful%20peice%20of%20hardware%20installed%20into%20this%20piece%20of%20crapola%20Operating%20System%20I%20like%20to%20loving%20refer%20to%20as%20Winblows%2010.%3C%2FP%3E%3CP%3EThank%20You.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%2C%20I%20would%20like%20to%20inform%20you%20that%20Intel%20has%20a%20driver%20release%20for%20their%20lovely%20piece%20of%20hardware%20dated%20June-2020%20so%20your%20driver%2C%20which%20I%20am%20being%20FORCED%20to%20use%20by%20your%20Winblows%20Operating%20System%20is%20NOT%20the%20best%20driver%20available%20and%20is%20in%20fact%2C%20at%2014%20years%20old%2C%20most%20likely%20the%20absolutely%20worst%20driver%20available.%3C%2FP%3E%3CP%3EI%20just%20thought%20someone%20should%20let%20you%20know%20because%20apparently%20you%20beleive%20you%20are%20correct%20in%20all%20matters%20on%20Winblows%20and%20this%20is%20clearly%20NOT%20the%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1667734%22%20slang%3D%22en-US%22%3ERe%3A%20I%20have%20an%20open%20ticket%20with%20Intel-I've%20posted%20it%20here-extremely%20frustrated%20Windows%2010%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1667734%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHI%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782793%22%20target%3D%22_blank%22%3E%40FooTek%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20read%20this%20article%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdevblogs.microsoft.com%2Foldnewthing%2F20170208-00%2F%3Fp%3D95395%23%3A~%3Atext%3DThe%2520dates%2520on%2520all%2520Windows%2Cbut%2520the%2520timestamp%2520stays%2520put.%26amp%3Btext%3DWhen%2520you%2520installed%2520a%2520new%2Cone%2520provided%2520by%2520the%2520manufacturer.%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdevblogs.microsoft.com%2Foldnewthing%2F20170208-00%2F%3Fp%3D95395%23%3A~%3Atext%3DThe%2520dates%2520on%2520all%2520Windows%2Cbut%2520the%2520timestamp%2520stays%2520put.%26amp%3Btext%3DWhen%2520you%2520installed%2520a%2520new%2Cone%2520provided%2520by%2520the%2520manufacturer.%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Dear Intel people, I am also going to post this directly into the Microsoft Community Forums - just so you know.

I have been using/configuring/maintaining and troubleshooting Winblows, Linux and Unix Operating Systems since Windows 95 was but a baby. I have NEVER in my 37 years of IT seen something as crude, unstable and NOT ready for public release as the "feature update" to Windows 10 2004.

It is, without a doubt the MOST pathetic, beta release of any Operating System, software or driver that's been release in all that time. Since the release of Winblows 10 I have implemented no less than 4 backup locations, one of which is offline, simply because MS can no longer be trusted to delivery a clock software much less a whole Operating System.

I set my feature updates to 365 days for a reason. This time I figured - it's been four months, surely MS has worked out all the beta bugs of their "Public Release" by now. I was TOTALLY wrong and will not do this again.

I don't really blame MS for this, I know they're mostly incompetent when it comes to feature updates, I blame myself for breaking the golden 365 day rule.

I am beginning to hate Microsoft with a passion normally reserved for love making!!
=============================
OK - With the above frustration out of the way, lets move back to a more professional attitude.

I am using Intel Memory and Storage Tool ver. 1.2.79 (most recent as of today).
I cannot optimize my 665p NvME drive, all other functions SEEM to be working as expected
I have installed Windows 2004 Build - 19041.508
When I check the driver in use on the NvME it states:
Provider: Microsoft
Driver Date: 2006-06-21 (a 14 year old driver - ffs MS has gone absolutely crazy)
Driver Version: 10.0.19041.1
Digital Signer: Microsoft Windows

This is obviously NOT ideal and I am trying to install the actual Intel driver for my NvME found here:

https://downloadcenter.intel.com/download/29172/Client-NVMe-Microsoft-Windows-Drivers-for-Intel-SSDs...

I have tried a manual install via: Client-64bit_f6flpy.zip - which resulted in Winblows telling the BEST driver is already installed.
I have tried installing via: Setup_NVME.exe - which resulted in your install program telling no supported devices were found

I have searched using Windows Update and no new drivers found because apparently that driver from 2006 is the BEST one to be used.

Dear Intel tech support, please help me get the proer driver for your wi=onderful peice of hardware installed into this piece of crapola Operating System I like to loving refer to as Winblows 10.

Thank You.

 

Microsoft, I would like to inform you that Intel has a driver release for their lovely piece of hardware dated June-2020 so your driver, which I am being FORCED to use by your Winblows Operating System is NOT the best driver available and is in fact, at 14 years old, most likely the absolutely worst driver available.

I just thought someone should let you know because apparently you beleive you are correct in all matters on Winblows and this is clearly NOT the case.

 

1 Reply