Can't Detach VHD

[perplex]

i never added the VHD, i think it was added because i plugged in a external hd with windows on it, and im assuming that had the VHD on it (wasnt my drive)

 

in computer management i click detach and it says the file location what isnt on my current pc, im assuming the external drive windows system, after i click ok it says the device is not ready

 

running windows 10

 

how so i force delete it? it only shows in computer management, and i cant assign it a letter path or delete volume, i can only turn it online and offline

 

 

[Oshino Shinobu]

If you turn it offline and then detach it, does it work? 

 

If not, try running Powershell as admin and use the Dismount-VHD cmdlet

 

EDIT: Looks like it may actually be created by the Windows Sandbox feature. See if that's enabled (Control Panel > Programs and Features > Turn Windows features on or off > Windows Sandbox). Or you can disable it through Powershell as well:

 

Disable-WindowsOptionalFeature –FeatureName “Containers-DisposableClientVM” -Online

[perplex]

4 minutes ago, Oshino Shinobu said:

If you turn it offline and then detach it, does it work? 

 

If not, try running Powershell as admin and use the Dismount-VHD cmdlet

offline does the same error

 

powershell says

 

Dismount-VHD : The term 'Dismount-VHD' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Dismount-VHD cmdlet
+ ~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Dismount-VHD:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

[Oshino Shinobu]

Just now, perplex said:

offline does the same error

 

powershell says

 

Dismount-VHD : The term 'Dismount-VHD' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Dismount-VHD cmdlet
+ ~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Dismount-VHD:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

 Looks like it may actually be created by the Windows Sandbox feature. See if that's enabled (Control Panel > Programs and Features > Turn Windows features on or off > Windows Sandbox). Or you can disable it through Powershell as well:

 

Disable-WindowsOptionalFeature –FeatureName “Containers-DisposableClientVM” -Online

[perplex]

3 minutes ago, Oshino Shinobu said:

 Looks like it may actually be created by the Windows Sandbox feature. See if that's enabled (Control Panel > Programs and Features > Turn Windows features on or off > Windows Sandbox). Or you can disable it through Powershell as well:

 

 

Disable-WindowsOptionalFeature –FeatureName “Containers-DisposableClientVM” -Online

 

ah looks like you are correct, it was sandbox, thanks

 

i never got sandbox to work though keeps saying -  error 0xc0370106 when trying to launch any ideas for that?

[Oshino Shinobu]

1 minute ago, perplex said:

ah looks like you are correct, it was sandbox, thanks

 

i never got sandbox to work though keeps saying -  error 0xc0370106 when trying to launch any ideas for that?

Not sure on that. 

 

An article I found suggests that KB4501375 could have caused it. Most of the June cumulative and security updates broke some pretty important Windows features, so I wouldn't be too surprised. If you haven't already, try applying July's updates and see if you get the same problems. 

 

EDIT: it also suggests that KB4497165 seems to be causing it. Uninstalling that (it's an update from May) supposedly fixes it.

[perplex]

4 minutes ago, Oshino Shinobu said:

Not sure on that. 

 

An article I found suggests that KB4501375 could have caused it. Most of the June cumulative and security updates broke some pretty important Windows features, so I wouldn't be too surprised. If you haven't already, try applying July's updates and see if you get the same problems. 

yea thats what i read too, how do you re apply the update?

 

maybe ill just keep waiting for them to fix, surly they know about it

[Oshino Shinobu]

Just now, perplex said:

yea thats what i read too, how do you re apply the update?

If you've already installed the new updates, then it's probably not that. 

 

Further on in the article, it says KB4497165 is causing it. Search to see if you have that installed and uninstall it. 

 

Can be done through installed updates in control panel. 

 

Quick PS to search for it if you want.

 

get-hotfix | findstr "KB4497165"

[perplex]

5 minutes ago, Oshino Shinobu said:

If you've already installed the new updates, then it's probably not that. 

 

Further on in the article, it says KB4497165 is causing it. Search to see if you have that installed and uninstall it. 

 

Can be done through installed updates in control panel. 

 

Quick PS to search for it if you want.

 

 

get-hotfix | findstr "KB4497165"

 

yea it doesn't let me uninstall it, no option

 

all good, ill just wait for them to fix, if they ever do...

[Oshino Shinobu]

Just now, perplex said:

yea it doesn't let me uninstall it, no option

Not sure on that then. Doesn't seem like MS has released an actual fix for it yet