[spacedesk Lea]

Hi @supchek,

1. Do you VPN enable? If yes, please disable it.
2. Do you have third party firewall or antivirus software on your machine? If yes, please make sure to include spacedeskService (C:\Windows\system32\spacedeskService.exe) in the exception list to allow incoming and outgoing connection.
3. If you are connecting over WiFi network, please check if your WiFi router settings has client/WiFi/AP isolation enabled. If this is enabled, it will prevent direct communication between connected devices/computers.
4. Please also make sure your current network profile is set to Private, via Windows Settings -> Network & Internet.
For more info please check the Troubleshooting -> Network Connection chapter in the user manual https://forum.spacedesk.netuser-manual/.

If the suggestions above did not help, could you please send us the diagnostic info in your primary machine.
Just open the spacedesk Driver Console -> Diagnostics, then click the “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 @npetroff,
Thanks for the feedback.
This ping result indicates that your primary machine cannot reach your Android device, please check your wireless network connection.

[spacedesk Lea]

Hi @pluto,
Thank you very much for sending the logs.
Please try to reboot your primary machine and try again with spacedesk Driver 1.0.46 installer.

[spacedesk Lea]

Hi @zajacmarek48gmail-com,

Thanks for sending the diagnostic files.
It seems that you have splashtop’s lci_proxywddm installed on your primary machine.
If you have splashtop software installed, please open the splashtop Wired XDisplay Agent -> Advanced and uninstall the Virtual Display.

[spacedesk Lea]

Hi @wuzhengxuan,

Unfortunately *.7z file is not allowed as attachments.

Could you please follow the steps below:
– open the spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– 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 @log,

I see.. can you quickly try to disable the touchscreen and only enable the pen in your spacedesk Android Viewer app -> Input devices settings?
And check if it still freezes your primary machine..

[spacedesk Lea]

Hi @lenny,

Ah I see.. if you want a lower resolution, you can select a lower custom resolution in the spacedesk iOS Viewer settings, then you can switch the to that lower resolution via Windows Display settings OR just uncheck the use of native resolution in the Viewer settings so it will automatically use the custom resolution.

[spacedesk Lea]

Hi @ouyangyinling,

Thanks for sending your dump file.

The problem seems to be the USB driver used by the mobile phone for USB Tethering. Please check the attached dump analysis.
Can you check if there is maybe a newer version of this mobile phone USB driver and try to update?

In some cases, when spacedesk is connected over USB tethering connection, the USB driver used by USB tethering network causes a BSOD crash.
Please try to update the Windows USB driver via Windows Update.

附加檔案:

你必須 登入 才能查看附件檔案。

[spacedesk Lea]

Hi @log,
Thanks for the feedback.
It seems like a system crash.

For further analysis, can you please check if you can find a recent dump file (time stamp should be the same as when the pen input issue happen) in C:\Windows\minidump.
Please save it in a folder, then right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.

[spacedesk Lea]

Hi @lenny,

Thanks for sending the diagnostic logs.

We noticed that on your second diagnostic info, your iPad client was assigned to Wall2 / WallIndex set to 2.
And that’s why it’s displaying a zoomed in imagae because the screen is only displaying the 1152×864 portion of the Videowall 2 which has 4K resolution (3840×2160) by default.
Try to right-click the client connected in the spacedesk Driver Console and select -> Unassign, to switch it to extension mode then the touch should work again.

FYI: The touch screen on spacedesk currently not supported if the viewer/client is assigned to a Video Wall.

[spacedesk Lea]

Hi @1205061869qq-com,

Can you please try with spacedesk Windows 7 Viewer (desktop version 0.9.39)?
It’s a newer version than the Windows 10 Viewer from Microsoft Store.
You can download it directly from the website https://forum.spacedesk.net.

[spacedesk Lea]

Hi @invaliderror,

Thanks for the feedback.

We were able to reproduce the increasing dedicated GPU memory (but no system crash yet..).
We will continue analyzing it and get back to you as soon as we have news regarding this issue.

In the meantime, please run dxdiag.exe, then click “Save All Information” then send us the dxdiag.txt of your primary machine.

[spacedesk Lea]

Hi @lenny,

Thanks for the feedback.

For further analysis, can you please send us the spacedesk diagnostic files with the settings changed.
Just recreate the settings (with viewers connected) where touch did not work then open the spacedesk Driver Console -> 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 @invaliderror,

Thank you very much for reporting this issue.
We are currently investigating and trying to reproduce this issue.

For further analysis, could you please send us the diagnostic info of your primary machine?
Just open the spacedesk Driver Console -> Diagnostic -> 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 @lenny,

Can you please tell us the specific settings you changed?

[spacedesk Lea]

Hi @avitmechanic,

You can try to disable the touchscreen input in the spacedesk Viewer Settings.

[spacedesk Lea]

Hi @zirin,

spacedesk Service Tray Window can only be hidden during runtime by clicking the View -> Hide taskbar icon -> click “X” button to close.
It will always pop-up whenever there’s a new viewer connection or after PC restart.

This is the current design in the spacedesk Service Tray to indicate that there’s a new active spacedesk connection (in case there’s an unauthorize connection) since security feature is not yet available.

[spacedesk Lea]

Hi @npetroff,

Thanks for sending your diagnostic logs and for checking the router settings.
Can you easily try to ping the IP address of your secondary device from your primary machine (vice versa) to check if both PC/devices are reachable to each other?

By the way, which spacedesk Viewer app are you using? Is it Android/iOS/Windows?

[spacedesk Lea]

Hi @wahab,

Unfortunately, we cannot download your attachment, *.7z is not allowed.
Could you please follow the steps below on how to get the diagnostic logs for this issue for further analysis.

– open the spacedesk Driver Console app -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and reproduce the issue then disconnect manually
– 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 @npetroff,
Thanks for the initial info.
Can you please check your WiFi router if there’s a client/WiFi/AP isolation setting enabled?
This setting prevents direct communication between connected devices/computers.

By the way, we cannot open your attached diagnostic logs, please re-attach it as *.zip file.

PS: We moved your post in a separate topic to avoid confusion.

[spacedesk Lea]

Hi @log,
Are you using the most recent spacedesk Driver v1.0.46?
Which screen is frozen after pen input? Is it the secondary viewer screen only or also the main monitor?

[spacedesk Lea]

Hi @bensmir,
Your setup looks good.
There shouldn’t be a problem with spacedesk connection with your crossover ethernet setup.

[spacedesk Lea]

Hi @louisa,

You can easily switch the spacedesk display to Extension mode via Windows Display Settings or via Display Switch (Windows logo + P hotkey).
For assistance, please read the Configuration and Settings -> Windows PC (Primary Machine) chapter in the user manual.
https://forum.spacedesk.netuser-manual/

[spacedesk Lea]

Hi @soundblaster,

Could you please quickly try this: run services.msc on your primary machine, then find spacedeskService and try if you can easily stop-start it.

For further analysis, please go to spacedesk Driver Console -> Diagnostics, 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 @james,
On which drawing app did you try to use spacedesk with Sonar Pen? Is it Photoshop?

[spacedesk Lea]

Hi @vickyscalling,

We are currently fixing the attach button. In the meantime, could you please the spacedesk Driver Console -> Network, click the adapter interface underneath and check its Network profile, if it’s private or public.

If it’s public, please try to switch it to private via Windows settings -> Network & Internet, click your current network then on properties -> select Private.

[spacedesk Lea]

Hi @kabo,

We are currently fixing the attach button.
In the meantime, could you please open the spacedesk Driver Console and check for any Incompatible Software underneath Diagnostics.
For further assistance, please also check the troubleshooting chapters in the user manual https://forum.spacedesk.netuser-manual/.

[spacedesk Lea]

Hi @vickyscalling,

For further analysis, could you please send us the spacedesk diagnostic info of your primary machine?
Just open the spacedesk Driver Console -> Diagnostics, then click the “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 @sp,

Thanks for sending the diagnostic info.
Based on the logs, you have an old Intel graphics adapter with WDDM 1.1.
Desktop Duplication on primary machine is not supported if you have an old version of graphics adapter with less than WDDM 2.0 version.
Just download the latest driver version from Intel website OR if it did not work try to downgrade the graphics driver to Microsoft Basic Display driver via device manager.

Please take note that downgrading to Microsoft Basic Display driver might introduce another problem in spacedesk e.g. device error code 43 in spacedesk Graphics Adapter in device manager.

For more info please check the Troubleshooting -> Known Issues, Problems and Limitations -> Windows 10 Desktop Duplication (mirror) option not available chapter in user manual https://forum.spacedesk.netuser-manual/#item_484.

[spacedesk Lea]

Hi @aquelemesmo,
Could you please try the methods suggested here

[spacedesk Lea]

Hi @hamakaze,
We have sent you the spacedesk Driver v1038 installer through your registered email address.
Please check.

For further assistance, please also check the Uninstall troubleshooting chapter in the user manual https://forum.spacedesk.netuser-manual/.

[spacedesk Lea]

Hi @zorzini,

spacedesk does not handle the desktop background image, you can only configure it via Windows Settings.

[spacedesk Lea]

Hi @sermalfilms,

Thank you foe sending the diagnostic info.
Based on the logs, you have one of the incompatible software present in your primary machine – splashtop.
You have to uninstall its Virtual driver first before connecting to spacedesk.
Just open the splashtop Wired XDisplay Agent -> Advanced, then uninstall their virtual driver.

[spacedesk Lea]

Hi @ymclozy,
We have sent you the spacedesk Driver v1043 installer through your registered email address.
Please check.

For further assistance, please also check the Uninstall chapters in the user manual https://forum.spacedesk.netuser-manual/.

[spacedesk Lea]

Hi @heoyum,

For further analysis, please follow the steps above to generate a complete spacedesk diagnostic logs, then attached the zip file on your next reply.

[spacedesk Lea]

Hi @xtreme1,
Unfortunately, no more suggestion at the moment.
This issue is already forwarded to the developer. We will get back to you as soon as we have news regarding this topic.

• 該回覆由 spacedesk Lea 於 2 years, 5 months ago 修改。

[spacedesk Lea]

Hi @heoyum,

Can you please tell us your primary and secondary machine’s operating system?
Primary machine – Windows 7/8.1/10/11?
Secondary machine – Android/iOS/Windows?

Are you using the most recent spacedesk Driver and Viewer version?

For assistance, please also check the troubleshooting chapters in the user manual https://forum.spacedesk.netuser-manual/.

If the troubleshooting chapters did not help and if you have Windows 10/11 as primary machine, could you please send us the diagnostic logs for this issue?
– open the spacedesk Console window app by clicking the spacedesk tray icon on your task bar’s notification area
– click the Diagnostics on the left side panel
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– 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 於 2 years, 5 months ago 修改。

[spacedesk Lea]

Hi @usernameak,

Did you enable the Pen output in the spacedesk Viewer settings -> Remote Control?

On which drawing app? Paint? Photoshop?
Is the issue only in pen eraser? how about the other drawing tools e.g. pencil, brushes, etc?

[spacedesk Lea]

Hi @cyrex,

Did you click the “Uninstall” button?
If yes, please reboot your primary machine and check again.

• 該回覆由 spacedesk Lea 於 2 years, 5 months ago 修改。

[spacedesk Lea]

Hi @chysioze,
RDP connection into secondary machine while spacedesk Viewer is connected should work and as long as the secondary machine and primary machine are connected on the same local area network.
And there should not be any spacedesk connection issue while another PC is connected to the secondary machine via RDP.

[spacedesk Lea]

Hi @nathan22211,
Did you also try to enable the Pen pressure in the Krita toolbar settings?
Please check this link.

Can you quickly try with other app if pen pressure will work with spacedesk (e.g. Microsoft Whiteboard)?

[spacedesk Lea]

Hi @nathan22211,
Is the Sonar Pen already calibrated?
Did you enable the Sonar Pen option in the spacedesk Viewer settings?

[spacedesk Lea]

Hi @sp,

For analysis, could you please send us the diagnostic logs of this issue.
Please follow the steps below:
– open spacedesk Driver console app -> Diagnostics
– click the “Download” button for Debug View, once the Debug View becomes available proceed to next step
– switch Diagnostic ON (make sure to click Yes in the User Account Control box to proceed)
– connect your iOS 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.

By the way, we moved your post to a new topic to avoid confusion.

[spacedesk Lea]

Hi @alitech,
Thanks for the feedback.

For further analysis, could you please also send us the debug view log of this issue.
Please follow the steps below:
– open spacedesk Driver console app -> Diagnostics
– click the “Download” button for Debug View, once the Debug View becomes available proceed to next step
– switch Diagnostic ON (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer apps 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 @xtreme1,

We don’t recommend using an older version of spacedesk. It contains various bugs that are already fixed in the most recent sapcedesk driver version.
If the custom resolution you selected don’t have a * in it, then it does not match the aspect ratio of the device’s screen, sometimes it keeps the aspect ratio (with black borders on the side) sometimes it’s not. This is an inconsistent behavior in spacedesk which is still present.

Could you please try this workaround and check if it works for you:
– on spacedesk viewer settings -> resolutions, enabled both native and custom resolution that don’t have * (e.g. 800×600)
– connect the viewer app
– open the display settings window on your primary machine
– switch the spacedesk display resolution from native to custom (maybe a few times) and check if it will eventually keep the aspect ratio upon switching to custom resolution.

[spacedesk Lea]

Hi @amfidiusz,
Thanks for feedback.
We are glad that it’s working now on your side.
We will definitely add the network profile in the troubleshooting procedure in the user manual.

[spacedesk Lea]

Hi @er1c-ma,
Yes, 2.0 will be different from the current BETA version.
Once 2.0 is released, the free version will only have limited features available in it.

[spacedesk Lea]

Hi @alitech,

Could you please try to “Clear Windows Display Settings” in spacedesk Driver Console -> Control, then try again with spacedesk.

[spacedesk Lea]

Hi @ruden,

Thanks for sending the diagnostic logs.
We are currently analyzing it.

While display the “display off”, can you please check if there’s a detached display in your primary machine’s display settings.

By the way, what is the operating system of your secondary machine? Android/iOS/Windows?
If it’s Windows, could you please send us the dxdiag info of this machine?
Just run dxdiag.exe the click “Save All Information” button, then send us the dxdiag.txt file in your next reply.

[spacedesk Lea]

Hi @amfidiusz,

Thanks for the info.

Are you sure there’s no client/AP/wifi isolation on your wifi router settings?

What is the current network profile of your wifi network in your primary machine? Private or Public?
You can check it in Windows Settings -> Network & Internet -> WiFi or Ethernet properties.
If the current profile is Public, please try to switch it to Private.

Can you also try to ping the IP address of your android tablet from your primary machine (and vice versa if you can do it easily)?
To check if both primary machine and secondary devices are reachable to each other.

Please also try to switch spacedesk server OFF-ON (to make sure that it’s running properly).

[作者]

文章