My issue is that I get a "pnp detected_fatal_error" blue screen when trying to create a new ReFS volume via veracrypt. I assume it crashes when the volume is mounted.
I upgraded from Windows 10 version 1803 to 1903 (19H1). This was working prior to the upgrade.
I realize this issue has been posted a few times, or a similar version of it. The issues I saw posted were about trying to mount ReFS veracrypt volumes resulting in a pnp detected_fatal_error BSOD.
I decided to format my drive with ReFS and then just create a standard encrypted file on it formatted NTFS until this issue is eventually fixed.
I'm assuming this came about due to Micro$oft cockblocking the ReFS feature removing it from all builds of Windows 10 other than Enterprise and Pro for Workstations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My issue is that I get a "pnp detected_fatal_error" blue screen when trying to create a new ReFS volume via veracrypt. I assume it crashes when the volume is mounted.
I upgraded from Windows 10 version 1803 to 1903 (19H1). This was working prior to the upgrade.
I realize this issue has been posted a few times, or a similar version of it. The issues I saw posted were about trying to mount ReFS veracrypt volumes resulting in a pnp detected_fatal_error BSOD.
Here is an example of this:
https://sourceforge.net/p/veracrypt/discussion/technical/thread/88b66508d3/
I decided to format my drive with ReFS and then just create a standard encrypted file on it formatted NTFS until this issue is eventually fixed.
I'm assuming this came about due to Micro$oft cockblocking the ReFS feature removing it from all builds of Windows 10 other than Enterprise and Pro for Workstations.