Jump to content

Windows 8.1 issue: "\System Volume Information" on attached VHDs


ppgrainbow

Recommended Posts

Does anyone have any idea on how to stop File Explorer from automatically creating the "\System Volume Information" on VHD hard disk images that are mounted as a drive?

I have a MS-DOS FAT formatted VHD that were created in Virtual PC 2007 when I was on Windows Vista for nearly three years.

MS-DOS 6.22 and below only supports the FAT partition and has no support for long file names at all.

If I try to attach the VHDs with one click using File Explorer, the "\System Volume Information" gets automatically written to the attached VHD and it ends up corrupting the volume label when running MS-DOS on VPC 2007 or Hyper-V! Here's an example screenshot of what it looks like:

SVI_VHD.thumb.png.32cc38fdfdc47f5539aadc2da2c9d5ea.png

The "\System Volume Information" is only used for System Restore points and in my opinion, it shouldn't be created when another internal hard drive doesn't have a System Restore point enabled.

Is there a way to stop File Explorer from automatically creating the "System Volume Information" folder to the attached VHD? :(

Link to comment
Share on other sites


59 minutes ago, jaclaz said:

I already prevented the System Volume Information folder from being written to a USB drive. It had nothing to do with preventing the System Volume Information folder to being automatically written to an attached VHD.

What I did was to disable Windows Search in Administrative Tools under Services. That way whenever I attach a VHD, the "\System Volume Information" folder won't be written anymore. :)

Link to comment
Share on other sites

38 minutes ago, ppgrainbow said:

What I did was to disable Windows Search in Administrative Tools under Services. That way whenever I attach a VHD, the "\System Volume Information" folder won't be written anymore. :)

Good. :)

jaclaz
 

Link to comment
Share on other sites

^_^

By the way, if I want to open individual participants rather than mounting the whole virtual hard disk image (VHD), I can always use ImDisk. :)

I got Windows Search disabled before on Vista and I did it again on Windows 8.1.

Edited by ppgrainbow
Link to comment
Share on other sites

56 minutes ago, ppgrainbow said:

^_^

By the way, if I want to open individual participants rather than mounting the whole virtual hard disk image (VHD), I can always use ImDisk. :)

Well, not really-really, through IMDISK you are still mounting a volume (as opposed to the "whole disk" and possibly multiple volumes) only you are doing it at a different level of integration to the OS, if you want to actually "open" a volume (without mounting and read only), 7-zip is better suited (limited to RAW files or fixed size .vhd's) or Winimage (R/W, with some hiccups, if I remember correctly).

jaclaz

 

Edited by jaclaz
Link to comment
Share on other sites

3 hours ago, jaclaz said:

Well, not really-really, through IMDISK you are still mounting a volume (as opposed to the "whole disk" and possibly multiple volumes) only you are doing it at a different level of integration to the OS, if you want to actually "open" a volume (without mounting and read only), 7-zip is better suited (limited to RAW files or fixed size .vhd's) or Winimage (R/W, with some hiccups, if I remember correctly).

jaclaz

 

The VHD are actually dynamic to conserve disk space.

Speaking of WinImage, why does the software have some hiccups when it comes to read/write operations? It hasn't been updated since April 2013.

Link to comment
Share on other sites

8 hours ago, ppgrainbow said:

The VHD are actually dynamic to conserve disk space.

Speaking of WinImage, why does the software have some hiccups when it comes to read/write operations? It hasn't been updated since April 2013.

Well, the fact that Winimage hasn't been updated means nothing, the software dates back to 1993 or 1994 originally, and it's not like anything actually happened in the meantime since 2013, except - maybe - the coming of the .vhdx format.

I seem to remember I had some issues in particular setups (non-standard "sectors before"), but a lot of time have passed so I am not too sure.

To save space do yourself a favour and use a sparse file (on NTFS of course) instead of a dynamic .vhd.

jaclaz
 

Link to comment
Share on other sites

1 hour ago, jaclaz said:

Well, the fact that Winimage hasn't been updated means nothing, the software dates back to 1993 or 1994 originally, and it's not like anything actually happened in the meantime since 2013, except - maybe - the coming of the .vhdx format.

I seem to remember I had some issues in particular setups (non-standard "sectors before"), but a lot of time have passed so I am not too sure.

To save space do yourself a favour and use a sparse file (on NTFS of course) instead of a dynamic .vhd.

jaclaz
 

That sounds like a giid idea. Any idea how can a sparse file on a NTFS volume can be created?

Link to comment
Share on other sites

Check this first thing:

http://www.opalapps.com/sparse_checker/sparse_checker.html
 

Here you can find a "collection" of more related tools:

http://reboot.pro/topic/20487-any-tut-on-expanding-c-partition-on-many-ramdisk/
http://reboot.pro/topic/20487-any-tut-on-expanding-c-partition-on-many-ramdisk/?p=192898

There is also a built-in command in fsutil:

https://technet.microsoft.com/en-us/library/cc788025(v=ws.11).aspx

but it cannot - I believe - create sparse files directly.

jaclaz


 


 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...