[Myron]

Installed beta RC v1.0.29 and all is well again. Thank-you. 🙂

[Myron]

I was lucky. I had a system restore point I could use to roll-back the system configuration.

[Myron]

I will wait until SpaceDesk updates the software so as not to trigger this Hyper-V fault. I don’t currently have a machine I can test this workaround. I don’t know what else gets disturbed within the operating system.

A VM I use under Oracle’s Virtual Box now constantly Blue Screens Windows 10 after I’ve I encountered the buggy SpaceDesk beta, but it’s something I can live with.

So, for the people who have a dead Hyper-V and WSL installations, has this workaround brought it all back to life?

• Diese Antwort wurde geändert vor 2 Jahren, 10 Monaten von Myron.

[Myron]

Had the same problem. Not just WSL. Hyper-V breaks as well as Oracle Virtual Box. All virtualisation tools seem to be compromised by spacedesk_driver_Win_10_64_v1027_BETA.

I was lucky I had a system restore point before I installed spacedesk_driver_Win_10_64_v1027_BETA. Simply uninstalling SpaceDesk does not fix Hyper-V and related software components.

• Diese Antwort wurde geändert vor 2 Jahren, 10 Monaten von Myron.

[Myron]

Just using Windows Defender that’s built in. Will check the software within the next few days.

[Myron]

More information:

When the Task Manager is on the extended display on the Android 5.1 tablet all appears to be fine. If the display is idle of nothing on it and no activity then on the Android Tablet the display is frozen on whatever was displayed on it last. Windows 10 shows that the extended display does not exist. Space desk driver on the primary Windows 10 machine is showing as idle and no remote remote network connections.

A few seconds after I double clicked the system tray icon to show the driver’s status window on the Android tablet it shows that the display is not connected and the network connection between the spacedesk driver and the app on the Android tablet was re-established.

It looks like the data connection over the WiFi is disconnected either from the Andoid App or the spacedesk driver and when I bring the spacedesk driver status to the foreground, after a few seconds the connection is established and the extended display resumes.

Android app’s option to auto-reconnect is turned on. Automatic connect is off. Automatic server discovery is on.

Hope this feedback helps.

[Myron]

With YUV444 compression settings on and task manager NOT displaying in the viewer screen.

[Myron]

Android version is 5.1

[Myron]

It’s happened again. As I type this I can’t move the cursor to the second display on the Android tablet. Windows 10’s display settings shows that there is only one monitor. The desktop is still being shown on the second display on the Android tablet and is static. I extended the display and it’s has been about an hour without me even moving the mouse pointer onto the extended second screen. The Spacedesk server’s status is „ON (idle)“.

I tapped the screen on the Android tablet which then the app changed it’s display showing that the display is reconnecting, then connected and the extended display on the Android tablet is now active. The server status is now showing „ON (connected)“.

I don’t have a screen saver active on my laptop and the display did not blank/power off.

Server version is 1.0.12 and the Android app version is 0.9.76.

[Myron]

So far so good. Still testing, but today I have updated both the server on the Windows 10 machine and the app on the Android tablet.

[Myron]

I’ll get back to you regarding putting Task Manager on the extended display soon as that test being performed now.

In the meanwhile . . .

Image quality: About 75%
Encodong colour depth: Medium colour quality, medium speed (YUV 4.2.2)
Rendering colour depth: 16-bit

I’m going to try up the rendering colour depth to 24-bit.

Yes, the display was idle each time for a number of minutes. Don’t know exactly how long. At a guesstimate, 20 minutes.

[Myron]

What is the actual filename(s) of the old device driver file(s)?

[Myron]

Interesting. I wonder if it is possible to disable the unsupported driver. Where did you find the incompatible driver? Is this something that can be tweaked in the registry to disable it or maybe set the security ACL on the incompatible driver to prevent execution?

[Autor]

Beiträge