Support NeoGAF

[dgrdsv]

And this also occurs with Windows Server. Those idiots at Microsoft didn't plan this thing through....

Yep. It's also missing an interface to performance counters and I don't think that BypassIO is supported by that new driver.
Mind boggling that a company as big as MS would produce a new driver which would just miss half of features of the current one.

 

[winjer]

Yep. It's also missing an interface to performance counters and I don't think that BypassIO is supported by that new driver.
Mind boggling that a company as big as MS would produce a new driver which would just miss half of features of the current one.

No. BypassIO is not supported fully by this driver.

This is Microsoft, even when they do something right for once, they somehow manage to screw it up.
I swear Microsoft is by the biggest idiots in the industry.

 

[dgrdsv]

No. BypassIO is not supported fully by this driver.

 

[winjer]

I have that too. Though mine shows it's using volmgr.sys
What it seems to mean is that we get half of the benefits of BypassIO. It is skipping the filters but travelling in the volume stack.

 

[dgrdsv]

I have that too. Though mine shows it's using volmgr.sys
What it seems to mean is that we get half of the benefits of BypassIO. It is skipping the filters but travelling in the volume stack.

Well coupled with the fact that BypassIO isn't working on BitLocker encrypted drives and that Windows 11 22H2+ is encrypting all drives on installation on all PCs now I'd say that BypassIO as a feature is essentially dead now.

 

[winjer]

Well coupled with the fact that BypassIO isn't working on BitLocker encrypted drives and that Windows 11 22H2+ is encrypting all drives on installation on all PCs now I'd say that BypassIO as a feature is essentially dead now.

That is true. BypassIO seems to get disabled by everything. Not only Bitlocker. But also, split volumes. Indexing service. EFI partitions with only 100MB. Etc.
And it's also very limited, as it's a feature for Direct Storage. And with so limited adoption, it doesn't matter.
Also, this new driver also bypasses a ton of legacy layers, so it makes BypassIO a bit redundant.
And Direct Storage still works, it just doesn't do all of the BypassIO stuff.

With the stornvme.sys driver, BypassIO was working on my PC.

BTW, I prefer to have Bitlocker service disabled. After seeing Windows encrypt one of my drives without any input or authorization from me. Fortunately it was still waiting for me for the final go.
But after I saw several people only getting their drives encrypted by Bitlocker, and then not being able to decrypt the data and losing all of it. I prefer to have this service disabled.
Microsoft is too incompetent and untrustworthy for me to allow them to automatically start encrypting everything on my PC.

 

[dgrdsv]

BTW, I prefer to have Bitlocker service disabled. After seeing Windows encrypt one of my drives without any input or authorization from me.

I got that during 22H2 installation and then again after 24H2 installation.
TBF I've done some benchmarks with BL and w/o it and overall I'd say that I would prefer BL to be on. Will probably just leave it on after the next clean Windows install.

 

[moogman]

That is true. BypassIO seems to get disabled by everything. Not only Bitlocker. But also, split volumes. Indexing service. EFI partitions with only 100MB. Etc.
And it's also very limited, as it's a feature for Direct Storage. And with so limited adoption, it doesn't matter.
Also, this new driver also bypasses a ton of legacy layers, so it makes BypassIO a bit redundant.
And Direct Storage still works, it just doesn't do all of the BypassIO stuff.

With the stornvme.sys driver, BypassIO was working on my PC.

BTW, I prefer to have Bitlocker service disabled. After seeing Windows encrypt one of my drives without any input or authorization from me. Fortunately it was still waiting for me for the final go.
But after I saw several people only getting their drives encrypted by Bitlocker, and then not being able to decrypt the data and losing all of it. I prefer to have this service disabled.
Microsoft is too incompetent and untrustworthy for me to allow them to automatically start encrypting everything on my PC.

When I had an issue which my Bitlocker and needed the key, I was pleasantly surprised that MS hold it on your Microsoft online account. It could be considered a security flaw to be fair, but it got me out of a big issue at the time.