View Single Post
Old 10-11-2016, 10:41 PM   #325
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,367
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by rtiangha View Post
Well, yeah. One would hope that if they fixed it for one file system, it'd be fixed for all. Looks like it hasn't, though.

It really makes me wonder what they're doing though when it comes to mounting mass storage devices in these newer versions of Windows. Are they trying to be more strict about file system standards and specifications in order to implement security features to prevent the mounting of malicious volumes or something? Because I can't figure it out. Hopefully this all gets sorted out by the next general release next year.
It seems as if any modification from the stock boot sector (AKA VBR) structure makes Windows 10 unhappy. I suspect that you are correct in thinking that Microsoft is treating all modifications as being malicious.
DNSB is offline   Reply With Quote