Windows 10: HYPER-V VM via RDP - Cannot install Pgms !!!!!

Hi there

Trying to install programs while connected via RDP (the normal way of accessing your HYPER-V VM remotely).
Cannot install programs.

This seems a bit daft - I can't always be at the console of the HOST machine - I usually access VM's remotely anyway.

cheers
jimbo

:)

 

Hyper-V issue on Windows 10

Hello, thanks for the reply.

I tried different ways.

One virtual adapter for Hyper-V manager and Network application on VM. Connected to VM via Hyper-V and the via RDP.

Then I added second virtual adapter dedicated for RDP only.

No success.

btw my laptop is Lenovo T460. No broadcom adapters inside.

 

Windows 10 Hyper-V disconnecting with "Video Remoting was disconnected"

I'm using Hyper-V. Win 10 Pro was installed on a clean PC, not by update. At some moment (not from the beginning) it had lost ability to connect to a VM. All I see is constantly blinking black screen with a message "Video Remoting was disconnected". I can
connect via RDP client, but not via Hyper-V "direct" connection.

It doesn't work even with a fresh new VM with clean VHD. Doesn't matter if I switch "Enhanced session" on/off, or maybe add/delete virtual video adapter. So basically I can't really create a new VM, because I need at least to install an OS and I can't.

By the way, the issue seemingly appeared near the time Hyper-V received the update adding virtual video adapter support. But thanks to the glorious and magic new Windows Update I never had a chance to know what exactly changed in my OS before the issue appeared.

I already had Hyper-V reinstalled, changed nothing. What else can be done?

 

The fact that there's an error message displayed saying it's not permitted says this was done on purpose as opposed to it being simply a bug. I wonder what the reasoning would be to prevent installing via RDP?

 

Hi there

Got round the problem

Mapped the tsclient and then connected that as a Network drive --then it worked.

(Testing with a small install before I try Office / photoshop etc). I certainly don't want to COPY all to local drives so I'm glad the tsclient trick worked).

Cheers
jimbo

 

EDIT: Seems you solved it while I was composing this post.


Jimbo, reading that screenshot "between the lines" (if that's possible when we talk about an image *Smile), it looks like you are trying to install a program on your Guest (RDP host) using installer on your host (RDP client). If that's true, have you tried to copy the installer to RDP host and install from there?

 

Hi there

Yes - as above -- map the TSCLIENT drive as a network drive. Obviously I didn't want to copy programs to local drives before install -- that would make it horrible (and wasteful) if I have several machines.


I don't think the RDP error though is a specific W10 error - I remember something like that on earlier releases.

Cheers
jimbo.

 

It has to do with elevation / UAC. This article does not describe your now solved issue per se but points to right direction: A Black Screen Appears During a Remote Assistance Session in Windows 7

 

I think that error message is poorly worded. I think what it means is "cannot install from a remote desktop connection *folder*" RDP's tsclient file redirection is a bit goofy and doesn't fully support all filesystem functions (basically, it has to copy the file to a local temp folder first then do operations locally).

 

You have to copy the installer file to the machine you want to install it with. Then delete the installer after. It happens mostly when the installer file has to be decompressed first before the installation itself.