Now, I thought that you had installed this via Chocolatey, not the Windows installer, though. Based on other threads.
I did install via Chocolatey does that have something to do with it?
Yes, a lot. Chocolatey is its own package management system. So Get-WmiObject knows nothing about it and can't interact with it. It's not "installed" in Windows terms, it's just "sitting there."
Actually, no. It is almost always there for windows to see. Because most chocolatey installs actually use the default windows installer. Just with a /silent switch (or whatever is appropriate).
so by this information, one of the above commands should have worked?
Not reliably. Only in the case, which might be "sometimes" and might be "often" and might be "almost always", where the one package manager used the other. So no matter how often it works, it's not "meant to work" and works only by coincidence. The coincidence might be really often, but it is still coincidence and not working by design.
@dustinb3403 I did what you said to do, then i realized i missed a step, cause i couldn't find the file he told me to, cause it wasn't exactly the same as he put into the post.
then i installed, and ran that command, just booted my VM.
@Dashrender Ugh Powershell - Don't even. If I can avoid using it I do..
The reality is that us Windows Admins need to stop avoiding it. 😞
sigh agreed... but I protest...
Hey, getting me to use the Linux CLI is a step forward,.. I know (a few of) the commands now,.. while I just may no recall the context. I was able to find the mount that was at 100% usage yesterday using df -h... so that is a move forward..
Not surprising. Hyper-V isn't really meant to be used in that way aside from admin tasks once in a while. It's really meant to be used to run servers/services. Not a desktop you access through it's own console.
That's why I am not completely shocked. But since Hyper-V has replaced VirtualPC and is being promoted for this specific use case I am a little surprised that getting it competitive with VirtualBox has not been a priority.
This is a maintenance release. The following items were fixed and/or added:
VMM: fixed an issue with Windows 10 guest kernel debugging over the network for Hyper-V paravirtualized VMs
VMM: fixed a bug which prevented reading the saved state of the 'PATM' unit from VirtualBox 4.3.x (bug #14512)
GUI: changed default OS type for Windows from Windows XP to Windows 7
GUI: added another pre-defined guest screen resolution (bug #14384)
GUI: fixed update check which was broken due to changing the location of the root certificates (bug #13096)
GUI: fixed issues with synchronization of Caps lock / Num lock / Scroll lock on Windows hosts (bug #14302)
GUI: don't crash during VM shutdown if 2D video acceleration and 3D support are enabled (Mac OS X hosts only)
GUI: several seamless fixes for certain X11 window managers, also when used in multi-screen setups
GUI: Log window size, position and cursor-position fixes
Audio: fixed playing leftover/deprecated audio samples
Audio: fixed playing audio after suspending the host (5.0 regression; Linux hosts using the ALSA backend)
Audio: fixed playing short audio samples which were chopped off formerly
Audio: fixed distortions on OS X when the sample rate of the guest stream and host device don't match
Storage: fixed raw disk access and flat VMDK image access which would be always opened readonly (5.0.2 regression; bugs #14425, #14461)
Storage: fixed initial encryption of VDI images after they were compacted (bug #14496)
VGA: fix for certain graphics modes (bug #14516)
NAT: don't freeze while the VM is paused if the network attachment mode is changed from/to NAT with activated port forwarding
OVF: fixed duplicate USB controller entries in exported OVA/OVF (bug #14462)
Shared Folders: fixed a path separator issue (bug #14434)
Drag and drop: fixed crashes on OS X hosts when doing host-to-guest transfers
VBoxManage: another attempt to not deny changing the network adapter type at VM runtime (5.0 regression; bug #14308)
VBoxManage: fixed broken guestcontrol <VM-Name> list command (5.0 regression)
VBoxManage: fixed broken Guest Control stdout/stderr output (5.0 regression)
Mac OS X hosts: fixed remaining problems with activated SMAP (Broadwell and later; bug #14412)
Mac OS X hosts: fixed broken 3D support (5.0.2 regression; bug #14476)
Linux hosts: Linux 4.2 fix
Linux hosts: don't crash on older Linux distributions if the DBus service isn't running (bug #14543)
Windows hosts: fixed the VERR_LDR_MISMATCH_NATIVE error message (bug #14420)
Windows hosts: fix for Windows 10 build 10525 and later (bug #14502)
Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437)
Windows hosts: prevent intermittent host network disconnects during VM start/shutdown with bridged networking (bug #14500)
Windows Additions: fixed the call to the memory allocation function (bug #14415)
Linux Additions: be more forgiving if the compilation of the vboxvideo module fails (bug #14547)
X11 Additions: fixed a number of small issues with dynamic resizing and full-screen and seamless modes.