CO-Release Build 22000.160 out to Dev and Beta Channel KB5005189

That date showing on the Driver properties by MS is not a real date of the driver, you can see that the driver on Windows 10 has the same date.

__________________________________________________________________________________

Now I see what you mean fg2001. I don't know how I could have mist that. Thanks for pointing that out. I did try installing the driver from Samsung at the time of install however it would Not install. And the one from Microsoft worked perfectly without any fuss so I just kept the one from MS. So it would appear that I'm using the most current driver for Windows 11 correct?.... The 10.0.22000.1

Hi,

If you look at the driver details you can see the name of the files which really did not change, but you can find the date of the file looking in Windows\system32\Drivers which shows 6/5/2021 while on Win 10 it shows 4/9/2021.

The size of the file disk.sys is also different. 97KB on Win 10 versus 121KB for Win 11.

The other 2 files are also different in size and date.

As for installing different divers they need to have to proper signature or they will not install.

That is the version I have, but I couldn't say when.

After a reboot the taskbar is hiding again, not stuck showing anymore. Will amend what I had put in FH.

Cheers,
Drew![Image](https://learn-attachment.microsoft.com/api/attachments/6b0d0f55-0567-4140-83e3-ed20526c820e?platform=QnA

_____________________________________________________

Hi Drew,

     Sorry I must have mist your reply post. And I'm glad you have the Hide Taskbar Hiccup worked out for you. I think Windows 11 build 22000.160 is working Very Well for me with little to No Major problems or as you know I like to call them Hiccups. 

I'm also wondering how many of us have tried the New Voice Typing in windows 11 build 22000.160 yet. I have been just messing with it and I think it's going to work out just Great as a New Improved feature to windows 11. Have you tried it yet?... to Activate or Launch press the Win-key + H

I see and your correct. I'm also seeing a fourth file

And of course mine does say 10.0.22000.1

I see and your correct. I'm also seeing a fourth file

And of course mine does say 10.0.22000.1

In my case I don't see the kxdiskprot, it may be specific for that type of NVMe.

Anyway, I just tried replacing the 3 files I have with the ones from Windows 10 and I will run the test again to see if it changes the results....

The results are different, actually worse than with the original drivers, I guess MS needs to sort this out...