VHD Attach

Here's an interesting tool for handling VHDs, worse our attention:

VHD Attach 2.10
http://www.jmedved.com/vhdattach/

VHD Attach 2.10
http://www.jmedved.com/vhdattach/

Have you tried the Beta version 3.0 which can also create VHDs?

TheHive

Thanks for pointing to this interesting app. With small enhancements like adding options (disk type: Fixed, Dynamic, Differencing) to Create VHD feature, and adding features like Add VHD to Boot Menu this app will fit the bill for a convenient basic shell VHD handler. Its better to group its commands under common Cascading Context Menu.

Its somewhat slow running though. Will invite the author to this forum.

Hopefully, VHD Director will be the "ultimate" app for advanced work with VHDs, if released at some point. But for routing tasks VHD Attach promises to be quite useful.

Have you tried the Beta version 3.0 which can also create VHDs?

Must have been recent update. Thanks!


Very nice gui. and the fact you can easily create vhd's. Even better.



What does 1000-Based mean






http://www.jmedved.com/vhdattach/faq/

• VHD cannot be attached when stored in a network location.
  Most probable reason for this is that Local Service has no rights on network location.
  Easiest solution is to go into Computer Management -> Services and Applications -> Services and there find “VHD Attach” service. Right-click properties and then go to Log On tab. Instead of Local System account select This account and fill your user data.
  After service restart you should be able to attach from network location also.

TheHive

Thanks for pointing to this interesting app. With small enhancements like adding options to Create VHD feature, and adding features like Create Dif VHD and Add to Boot Menu this app will fit the bill for a very basic shell VHD handler. Its somewhat slow though. Will invite the author to this forum.

Hopefully, VHD Director will be the "ultimate" app for advanced work with VHDs, if released at some point.

Good Idea to invite him to the forums.

What does 1000-Based mean

It serves to lie about disk size as much as manufacturers do (http://en.wikipedia....sumer_confusion)
E.g. 300GB disk will be in fact less than 280GiB.

Hi jmedved,

Welcome to Reboot forum! Good news travel fast, we just started the discussion about your tool, and you're already here... This forum has plenty of topics about VHDs, and your in-depth contribution is surely welcome.

For starters, have a look at this suggested ToDo List - what do you think about it?

Sadly, VHD Attach app doesn't work for me at all in ThinPC 7 32-bit, but works in WES7 64-bit (Error: "Can't find the file specified"). Any ideas?

Sadly, VHD Attach app doesn't work for me at all in ThinPC 7 32-bit, but works in WES7 64-bit (Error: "Can't find the file specified"). Any ideas?

Let me install ThinPC and debug it a little.

For starters, have a look at this suggested ToDo List - what do you think about it?

As far as planned future for VHD Attach goes, next version is planned to include creation of fixed disks. Sometime after that I plan to introduce conversion between fixed and dynamic disks.

Adding disks to boot menu is not planned for next few immediate versions. It is something I have been playing for a while but so far I haven't found a way that works satisfactory on all systems and locales where VHD Attach runs.

Sadly, VHD Attach app doesn't work for me at all in ThinPC 7 32-bit, but works in WES7 64-bit (Error: "Can't find the file specified"). Any ideas?

There were two issues here. One is that Thin PC comes without any .NET Framework so one needs to be installed. Other issue is that .NET 3.5 (used in VHD Attach) is not supported.
New version is available for download.

Thanks, will try. Do you use another .NET version now?

Thanks, will try. Do you use another .NET version now?

No, I still use .NET 3.5 (because it comes with Windows 7 out-of-the-box). However because of ThinPC, I added configuration files that tell .NET 4 that it is safe to run my program.

It appears from your website, you previously used Diskpart in this app. How did you check, if an attached volume was assigned a drive letter? I mean, its better to check than assign each time a different letter to this same volume at mounting.

It appears from your website, you previously used Diskpart in this app. How did you check, if an attached volume was assigned a drive letter? I mean, its better to check than assign each time a different letter to this same volume at mounting.

I leave all letter assignment work to Windows. I just check what they assign.
I used to check this with DISKPART but there was a lot of issues with keeping it straight on localized Windows versions (e.g. German). Now I am querying Windows API for that information.

I tested it on ThinPC, and it works great now.

The only thing at this stage, one would expect it to attach & detach VHD on double-click instead of opening the app window. A user needs to install .NET 4.0 to use the app.

I tested it on ThinPC, and it works great now.

The only thing at this stage, one would expect it to attach & detach VHD on double-click instead of opening the app windows. A user needs to install .NET 4.0 to use the app.

I might think about it for some future version but only as a non-default option. I think that this will generate more issues than it solves.