Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconsider VHDs being displayed by default, due to introduction of Dev Drives #2395

Closed
pethesdaniel opened this issue Jan 5, 2024 · 2 comments
Assignees
Milestone

Comments

@pethesdaniel
Copy link

pethesdaniel commented Jan 5, 2024

You mentioned in a previous issue that you consider VHDs detachable media and fair game. See: #2305

However, Windows 11 introduced Dev Drives with ReFS as a way for developers to store their source code and other files.

While source control does help to prevent accidental data loss, I feel like you should reconsider this approach or filter out Dev Drives, because Microsoft seems to consider VHDs a valid form of storage for important data and pushes users to use it by integrating it into the new Settings and Dev Home apps.

@pbatard
Copy link
Owner

pbatard commented Jan 5, 2024

This is interesting. Thanks for the heads up!

I guess the solution to that is pretty straightforward, since Dev Drives appear to always use ReFS for the main partition along with a 16 MB MSR preceding it (though of course we should not rely on the size of the MSR to be constant as it is set at Microsoft's discretion).

So I'm leaning towards filtering out any VHD that has a an MSR + ReFS default partition configuration, since this is not a layout that can be created by Rufus (the goal being to still allow Rufus to create single partition ReFS on VHDs, which it can do, without those being filtered out).

I'll be playing with Dev drives some more and hopefully, I can filter these out by default in the next release of Rufus, while leaving regular VHDs accessible, as they were before.

@pbatard pbatard self-assigned this Jan 5, 2024
@pbatard pbatard added this to the 4.4 milestone Jan 5, 2024
@pbatard pbatard closed this as completed in ebe01cc Jan 8, 2024
Copy link

github-actions bot commented Apr 9, 2024

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants