[spacedesk Lea]

Hi @willycia,
Thanks for the feedback.

Fix for the failing console diagnostic collection will be available in the next release.
In the meantime, could you please send us the following (if available):
– C:\Users\Public\Downloads\Debugview.log
– all spacedesk files available in C:\Users\Public folder
– run dxdiag.exe, click Save All Information, then save the output file (dxdiag.txt)
Please save all the files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

Could you please also check in the spacedesk Driver Console -> Incompatible Software if there’s any software/product currently active.

[spacedesk Lea]

Hi @willycia,
Could you please send us the diagnostic logs for this issue?
– open the spacedesk Driver Console window app by clicking the spacedesk tray icon on your task bar’s notification area
– click the Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and wait for the issue to happen
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @willycia,
Do you still have this error? Maybe you only need to reboot your machine.

If it did not help, please send us the following for further analysis:
– run dxdiag.exe on your primary machine, click “Save all information” and send us the output file
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF

Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

• This reply was modified 2 years, 8 months ago by spacedesk Lea.
• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Hi @alfredo_c,
I see..
Can you please try the suggestions from this link:
https://www.makeuseof.com/tag/fix-touchscreen-windows-10/

[spacedesk Lea]

Hi @alfredo_c,
Just for clarification, is your touchscreen problem on spacedesk viewer screen?
OR is it the actual touchscreen functionality problem of your laptop (even without spacedesk connected)?

[spacedesk Lea]

Hi @toslim33,
Thank you very much for sending the diagnostic logs.

Upon checking the logs, it seems that it did not capture the disconnect issue.
Did you switch ON the diagnostics collection and wait for the disconnect issue to happen before switching OFF?
If not, please try again with the steps below:
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– connect your viewer app and wait for the disconnect issue
– switch Diagnostic Collection OFF
– click Save All Information button

As for the ShadowPlay detection in the console app, you can properly switch off the ShadowPlay by switching OFF the In-game overlay settings in the Nvidia Geforce Experience settings.
If this is not possible anymore, please check your task manager if you can find the NVIDIA ShadowPlay Helper in the process list and try to “End task” it (then maybe reboot your machine).

[spacedesk Lea]

Hi @alfredo_c,
Thanks for the logs.
Upon checking the logs, it seems that spacedesk is already recognizing the touch input from your viewer app so it should already work.
Are you maybe sending a touchscreen input to a particular desktop application e.g. Photoshop or any 3D games (e.g. MS Flight Simulator)?

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Hi @dagni,
Can you tell us which old version of spacedesk did you use that can remember the wallpaper settings of your second display?

Based on our testing this is only possible if you set a Disconnect delay time (in seconds) via spacedesk Driver Console and reconnect the viewer before the disconnect delay timeout.

[spacedesk Lea]

Hi @wulf,
Thank you very much for sending the diagnostic logs.

Upon checking the logs, we cannot find any indications that could cause a display off/black screen issue on spacedesk server.
Could you please check/verify the following:
1. Please check your display settings window if you can find a detached second display while viewer is showing display off.
2. Are you connecting over the wifi network? Is the connection fast/stable/reliable?
Maybe the network is slow and causes a delay in the transmission of screen update over the wireless network and you just have to wait for a while for the viewer to show the screen update?
3. Maybe something in your AMD Radeon software settings. Can you please check in your Radeon Software settings -> Preferences -> In-game overlay, if it’s disabled? OR maybe check the other Graphics settings.

[spacedesk Lea]

Hi @omega087,

Can you further describe the problem?
Viewer cannot discover? Did you get an error code upon connect?
For assistance, please also check the Troubleshooting chapter in the user manual.
https://forum.spacedesk.netuser-manual/

If the troubleshooting did not help, please open the spacedesk Driver Console in your primary machine, click Diagnostics -> Save All Information.
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @09hjoesk,
Thank you very much for sending the requested logs.
Based on the setup logs, the uninstallation for spacedesk virtual HID device is hanging.
This is a known issue in that old installer version which we already fixed in the most recent version.
To solve this on your machine, please manually uninstall the spacedesk virtual HID device in Device Manager.

– open Device Manager by running “devmgmt.msc”
– click View tab -> Devices by connection
– scroll down and find spacedesk virtual HID Device
– expand first the spacedesk virtual HID Device and right-click “Uninstall device” each devices underneath it
– then right-click “Uninstall device” the spacedesk virtual HID Device

Then try again to update with the latest spacedesk installer (v1037).

For assistance, please also check the Uninstall on Windows Primary Machine -> Manual Uninstall (Troubleshooting Only)
https://forum.spacedesk.netuser-manual/#item_518

[spacedesk Lea]

Hi @wulf,
Please try this modified version of the script here:
https://www.dropbox.com/s/lrreareb96quvnr/2022_spacedeskDiagnosticTool_v2.zip?dl=0
Same instructions above, this time the script should create “spacedeskDiagnostics” folder.

[spacedesk Lea]

Hi @jamesson,
Thank you very much for sending the diagnostic logs and a short video of the issue.
It seems that the issue is somewhere in the settings of your Photoshop, since spacedesk can already receive the Pen input properly with another app.

Please check if the Pen Pressure is configured on your Photoshop brush settings.
reference: https://www.computerhope.com/issues/ch002027.htm

[spacedesk Lea]

Hi @monky,
Is your User account type Administrator?

[spacedesk Lea]

Hi @09hjoesk,
For further analysis, could you please send us the following:
– run dxdiag.exe on your primary machine, click “Save all information” and send us the output file
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF

Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @roland,
There are some workarounds that you can try, please check the Troubleshooting -> Network Connection -> VPN (Virtual Private Network) chapter in the user manual https://forum.spacedesk.netuser-manual/#item_493.

If it did not help, then there’s nothing else we can do but to disable your VPN for spacedesk discovery to work.

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Hi @leungzw,

spacedesk automatically configures the Windows Firewall to allow spacedeskService during installation, you can verify it via Control Panel\System and Security\Windows Defender Firewall\Allowed apps.

Maybe you can also try to manually create an Inbound/Outbound rules in the Firewall settings for spacedeskService.
spacedesk uses TCP port 28252.

By the way, what is the current network profile on your primary machine? Public or Private?
Are both WiFi network on primary machine and cellphone have the same network band/frequency (e.g. 2.4GHz or 5Ghz)?

[spacedesk Lea]

Hi @leungzw,
Thank you very much for sending the diagnostic logs.
Could you please check your (Router1’s) WiFi router’s network isolation if it’s active/enabled.
This setting prevents direct communication between connected devices. The only solution for this is re-configuring the router.

[spacedesk Lea]

Hi @leungzw,
For further analysis, could you please open the spacedesk Driver Console -> Diagnostics, then click Save All Information button.
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @jamesson,
Did you also calibrate the SonarPen? And allow the Microphone permission in the SonarPen settings?
If yes and it still did not work, please send us the diagnostic logs of this issue for further analysis.
– open spacedesk Driver Console -> Diagnostics in your primary machine
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue (by sending several SonarPen input from your Android viewer)
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @monky,
Please check the attached file for clear instruction with screenshots.

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @monky,

Could you please try the following on your primary machine.
– right-click C:\Windows\Temp folder -> Properties -> Security tab -> Advanced -> Permission tab -> Continue
– check if you find the Users or Authenticated Users and make sure it has Full Control access
If none, just Add -> Select a principal, then type “Users” and click Check Names and click OK
– Then make sure to check the Full Control access for the Users then click Apply -> OK.
After following the steps above try to run-install again the spacedesk MSI installer.

[spacedesk Lea]

Hi @wulf,

Thank you very much for sending the requested logs.

For the spacedesk Console app issue, we will release a potential fix for this issue in the next version.

For the display off issue, could you please download the spacedesk diagnostic script here, then extract it.
https://www.dropbox.com/s/okjvl3v4g8xmknq/2022_spacedeskDiagnosticTool.zip?dl=0

The folder contains spacedeskDiagnosticTool.cmd, just right-click it, then run as administrator.
On step 5 it will prompt you to reproduce the issue (by connecting the viewer app and wait for the issue to happen), make sure to do this before pressing any key to continue.
After the script is done, a folder will be created in the same folder as the script file which contains various log files that we need for analysis.
Please right-click it -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @jamesson,
Did you enable the SonarPen in the spacedesk Android Viewer settings -> Input Devices -> Pen -> SonarPen Stylus?
Please check the attached screenshot for assistance.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @angels11_6,

You can easily setup the layout of your video wall by setting the correct Position (X;Y) of each clients, in the Video wall settings tab (of spacedesk Driver Console).
For assistance, please check the Video Wall Configuration chapter in the user manual https://forum.spacedesk.netuser-manual/.

[spacedesk Lea]

Hi @wulf,

Could you please send us the current .NET Framework version of your primary machine.
Just run the Windows PowerShell as Administrator then type the command:

Get-ChildItem ‘HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP’ -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match ‘^(?!S)\p{L}’} | Select PSChildName, version

Then press the Enter send us the result via txt file or screenshot.
Please check this link for reference: https://www.windowscentral.com/how-quickly-check-net-framework-version-windows-10

Could you also please send us the following for further analysis:
– Dxdiag.txt file – just run dxdiag.exe on your primary machine, click “Save All Information”
– C:\Users\Public\spacedeskSetup.log file

Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

For assistance, you can also check the Troubleshooting -> Windows PC (Primary Machine) chapter in the user manual https://forum.spacedesk.netuser-manual/.

[spacedesk Lea]

Hi @pen1350,

Is it a flickering screen when you said “PC crashed for around 10 seconds”?
Can it still recover after disconnecting the spacedesk viewer?

Can you quickly check in spacedesk Driver Console -> Diagnostics -> Incompatible Software, if Nvidia ShadowPlay/In-game Overlay/screen recording is active?
If it’s active, please stop/disable your Nvidia ShadowPlay then try again with spacedesk.

If it did not help, could you please send us the diagnostic logs of the issue.
– open the spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue (then disconnect immediately)
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @lowik,
Unfortunately, we cannot see the image.
Could you please re-attach it?

[spacedesk Lea]

Hi @armada45

Thank you very much for sending the diagnostic logs.
Based on the logs, you have splashtop display hook driver (lci_proxywddm) running on your machine. This product is currently not compatible with spacedesk.
You have to uninstall it, then reboot before you connect a spacedesk viewer.

To uninstall, just open the splahstop Wired XDisplay Agent on your machine the click on Advanced, then Uninstall the Virtual display driver.
OR just open the spacedesk Drive Console -> Diagnostics -> Incompatible Software, then click the Uninstall button beside the lci_proxywddm driver, then reboot your primary machine.

[spacedesk Lea]

Hi @janichols,
If the suggestion above did not help, please try the instructions we have sent you on your registered email.

[spacedesk Lea]

Hi @janichols,

Can you please download the Microsoft Troubleshooter program here:
https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d

Run the “MicrosoftProgram_Install_and_Uninstall.meta.diagcab”, select Uninstalling.
If “spacedesk Windows DRIVER” is not on the program list, just select “Not Listed” then paste the product code of spacedesk_driver_Win_10_64_v0987_BETA.msi here: {CE7DC976-85B4-45B2-BDEB-A2C7B5BCA18F}

After that, please reboot your primary machine then try again to install the latest spacedesk msi installer from the website.

By the way, do you have third party antivirus software currently active on your primary machine?

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Hi @mshemeer,
We have sent you an email regarding your Windows Driver SDK inquiry. Please check.

[spacedesk Lea]

Hi @jeberhard,
We have sent you an email regarding your Windows Driver SDK inquiry. Please check.

[spacedesk Lea]

Hi @elfik,
Thank you for sending the video, and for verifying that you are using a virtual machine as primary machine.
spacedesk do not officially support virtual machines. You can install it there, but we cannot guarantee that it will work properly.

This is a known behavior of mouse pointer in virtual machines when there’s a second display connected.
We are actually not sure if this is a spacedesk issue or a limitation in virtual machines.

[spacedesk Lea]

Hi @elfik,
Are you maybe using virtual machine as your primary machine?
Yes, please also send the video, it will be very helpful for analyzing the issue. Thanks!

[spacedesk Lea]

Hi @elfik,

Could you please open the display settings window on your primary machine and check the position of your second display and if you are moving the mouse pointer in the right direction.

[spacedesk Lea]

Thank you very much for sending the log file. We are currently analyzing it. Can you please also send us the updated C:\Users\Public\spacedeskSetup.log and C:\Windows\INF\setupapi.dev.log too?

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Hi @kokko,
Routers can cause lags and latency. Bypassing them always improves performance.
Configure Windows 11 PC or iOS device as WiFi Access Point (Hotspot) and connect to it before connecting spacedesk.
USB Tethering achieves the same result.
Please check the chapter “Performance Tuning” in the instruction manual: https://spacedesk.net/user-manual

[spacedesk Lea]

Hi @lrbsb,
For further analysis, could you please send us the diagnostic logs for this issue?
– open the spacedesk Driver Console app on your primary machine, then click the Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @azzy,
Could you please quickly check if there’s any incompatible software present on your primary machine. Just open the spacedesk Driver Console -> Diagnostics -> Incompatible software.

For assistance, please refer to Troubleshooting -> Windows PC (Primary Machine) chapter in the user manual
https://forum.spacedesk.netuser-manual/.

[spacedesk Lea]

Hi @oberon23,
Thank you very much for the feedback.
By the way, can you tell us your primary machine’s operating system? Is it Windows 7/8.1/10/11?

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Please rename the msi file name from “spacedesk_driver_Win_10_64_v1037_BETA (1).msi” to “spacedesk_driver_Win_10_64_v1037_BETA.msi”, then try again with the script.

[spacedesk Lea]

Hi @panxinxin,
Can you tell us which spacedesk version did you install/uninstall?

Is your primary machine monitor still displaying properly after spacedesk uninstall and before restarting it?
Can you try to boot your machine in safe mode?
For assistance, please refer to this link https://www.drivereasy.com/knowledge/how-to-enter-safe-mode-in-windows-10/#why

[spacedesk Lea]

Hi @janichols,

Thank you very much for sending the logs. We are currently analyzing it.
For further analysis, could you please download and extract the zip file here: https://www.dropbox.com/s/rqayx759wdwmye2/msi_trace.zip?dl=0
Inside the folder, please copy the most recent spacedesk MSI installer (v1.0.37) then run the get_trace.bat script file.
The script will execute the msi installer (to reproduce the installation error) and will automatically generate a spacedeskmsi_trace.txt file, then please send the file to us after executing the failed msi installer.

[spacedesk Lea]

Hi @oberon23,

It seems to remember the last desktop mode (extension) even after you detach your primary monitor.
Could you please try the following workaround:
– attach your primary monitor
– connect the spacedesk viewer
– switch to projector mode / second screen only via display switch (Windows logo key + P)
– detach your primary monitor
Try to restart your primary machine this time without your primary monitor attached and just try to connect your spacedesk viewer.

[spacedesk Lea]

Hi @mikhal980,

Thank you very much for sending the requested logs.
Based on the logs, there’s a RPC_S_CALL_FAILED error (The remote procedure call failed) during spacedesk USB driver installation.

One of the causes of this issue:
– failed installation/uninstallation of software that may have left invalid entries in your system
– improper system shutdown due to power failure

Could you please try the following suggestions below:
1. Run services.msc then find Remote Procedure Call (RPC), and check if it’s running.
2. Make sure to install any pending Windows Update on your Windows Settings.
3. Your AMD graphics driver is not digitally signed, please try to repair/reinstall your AMD graphics driver. Just download the AMD Auto-detect tool here: https://www.amd.com/en/support, to update your AMD graphics driver properly.
4. Run Command Prompt as Administrator, then type the command: “sfc /scannow” and press Enter.

• This reply was modified 2 years, 8 months ago by spacedesk Lea.

[spacedesk Lea]

Hi @nekona,

Thank you very much for sending the requested logs.
Based on the logs, your primary machine – Surface Pro X is an ARM-based tablet which spacedesk driver do not support.

[spacedesk Lea]

Hi @apollo163,
Is this only happening on spacedesk screen? Or also in your main monitor?

Could you please send us the diagnostic logs for this issue?
– open the spacedesk Driver Console -> Diagnostics in your primary machine
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @itzzkaz,
Could you please check if there’s any incompatible software currently active on your Windows 11 machine?
Just run spacedesk Driver Console -> Diagnostics -> Incompatible Software.

If there’s none, could you please send us the diagnostic logs for further analysis, just follow the steps below:
– click spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @romans,

You can easily do this by switching to Desktop Duplication (mirror) mode via Display Settings so you can remotely access your main monitor screen.
For assistance, please check Configuration and Settings -> Windows PC (Primary Machine) chapter in the user manual https://forum.spacedesk.netuser-manual/#item_469.

[Author]

Posts