Hi @scholarly-hobbit,
Thanks for sending the diagnostic files.
However the diagnostic files are incomplete.
Some logs are missing which we need for further analysis.
Please make sure to follow these steps correctly:
– 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 disconnect issue
– switch Diagnostic Collection OFF
– click Save All Information button
Then send us the new diagnostic files.
Hi @jj737,
Thanks for sending the files.
If there’s no spacedeskSetup.log file generate, then it means the msi installer hangs before spacedesk driver installation even started.
In this case, we will request for the msi trace (msiexec.exe) of the spacedesk msi installer.
For assistance, please download the spacedeskMsiTraceGenerate.zip here:
https://www.dropbox.com/s/vr17lj6n63k52rh/2022_spacedeskMsiTraceGenerate.zip?dl=0
– extract the zip file
– copy the most recent spacedesk msi installer (spacedesk_driver_Win_10_64_v1046_BETA.msi) inside the folder then click the get_trace.bat
– the script will prompt you to enter the msi file name then press enter
– it will run the spacedesk installer until you encounter the error
– please send the spacedeskmsi_trace.txt generated inside the folder
Hi @kadyr414,
Is it a system crash (blue screen)?
Or is it only disconnecting immediately upon connection attempt?
If it’s only a disconnection issue, please send us the diagnostic logs, just follow the steps below:
– open the spacedesk Driver 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 disconnect 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.
Hi @joshsum,
Thanks for sending the diagnostic files.
However the diagnostic files are incomplete.
Some logs are missing which we need for further analysis (e.g DebugView.log and *.etl files).
Please make sure to follow these steps correctly:
– 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 (by sending touch input for several times)
– switch Diagnostic Collection OFF
– click Save All Information button
When I try to install SpaceDesk on my Windows 10 computer (With a Nvidia 940M) I got the “Installation error” everytime. It always happen at “Installing Spacedesk services”. How can I fix it? I cannot upload a log since I don’t even know where it is, sorry.
Hi @jj737,
I see..
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.
Hi @joshsum,
Can you please tell us your primary machine’s operating system? Is it Windows 7/8.1/10/11?
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.
Hi @jj737,
You mean any msi installer aside from spacedesk cannot be installed on your machine?
If that’s the case, then it’s probably an issue on your machine.
Unfortunately, no EXE installer available for spacedesk.
Hi @gfix,
So far We cannot reproduce this issue on our side.
Is it USB tethering or Android Debug Bridge cable connection?
For further analysis, could you please send us the diagnostic logs of your primary machine.
Just open the spacedesk Driver Console -> Diagnostics -> click 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.
Hi @wuzhengxuan,
Could you please check on your Device Manager (just run devmgmt.msc) if there’s a disabled “Virtual Desktop Monitor” and try to enable it.
Hi @wuzhengxuan,
Could you please check in the Windows Display settings if there’s a detached display. If it’s there, please attach it by selecting the Extend or Duplicate.
For details, please check the Configuration & Settings -> Windows PC (Primary Machine) chapter in the user manual https://forum.spacedesk.netuser-manual/.
Hi @log,
For further analysis 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.
Hi Spacedesk Lea,
I have disabled the In-game overlay of Nvidia Geforce Experience and have attached a screenshot regarding the same. Also I had also generated a new log after disabling the overlay. Please find both attachments below.
Please provide some solution for this.
Hi Spacedesk Lea,
Can you give instructions of how to disable Nvidia ShadowPlay/In-game overlay/screen recording (via Nvidia GeForce Experience window)
Hi @nightmare-maxwell,
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.
Hi @nirbhay,
Thanks for sending the diagnostic logs.
Could you please try to disable the Nvidia ShadowPlay/In-game overlay/screen recording (via Nvidia GeForce Experience window) on your primary machine?
Then please check if the mouse still freezes upon spacedesk connect.
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.
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.
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.
My spacedesk installation always fails. I have attached the logs and dxdiag. Any ideas?
1.
Pinging 192.168.0.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.2: bytes=32 time=11ms TTL=64
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
2. Android: Xiaomi Mi 9. I have a Windows PC
Hi,
I have a problem with this error (Error Code 2-5 | Error Info 0-5 | Connection time: 00:00:01). I can’t connect my tablet and phone with Spacedesk. I used in past Spacedesk, and everything was good, but today when I restarted Windows to factory settings (I have windows 11) with disks and I installed Spacedesk again on my PC, I can’t connect! Windows tells me:
spacedesk x10
Error – Duet Display, Splashtop, Fresco Logic, etc. Driver Detected – Incompatible Display Hook Driver!
Attached is a compressed zip folder with diagnostics
I need help
Update: I changed the resolution to lower via Safari HTML 5 VIEWER, screen went black, and then on iOS app before connecting. After I connected, everything was ok, touch screen and keyboard work, even the new resolution appeared in windows display settings, although it’s not active there. The picture quality isn’t very good, but the speed is better. For example, at original resolution video dragged on, while at low resolution it is almost normal. Thank you for advice!
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.
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.
Just to be sure, I tried again. Cleared all settings and walls, deleted all spacedesk folders, uninstal driver, restarted laptop, deleted app from iPad. I reinstalled and without any settings touchscreen and keyboard work. I created Wall, just changed iPad resolution from spacedesk driver – Wall and Control settings, but again touch screen and keyboard not working. The good thing is that at least the mouse works noticeably more stable at a lower 1152×864 resolution.
Hi, I first saved some file before the settings change, and then changed the iPad resolution everywhere. The image enlarged excessively and even a black screen appeared on both devices, on a laptop the icons were visible. Restarted laptop and reconnected, ipad image came up huge again. Then I noticed another place – CONTROL on wall settings, where the resolution was huge, so I changed it there too and now the image is fine, but the touchpad and keyboard don’t work.
I am sending you a pre-setup and post-setup diagnosis. You will be guided by the number, date and time in the file names.
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.
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.
I have tried “Save All Information” three times and the designated output folder remains empty even after installing DebugView, running debug mode for the few seconds it takes to get 20GB of “Dedicated video memory” by wiggling a window on the remote display and turning it back off before clicking the button.
If it is a systemic problem, it shouldn’t take more than a few seconds to duplicate:
1- connect a remote display
2- open Task Manager in detail view showing dedicated GPU memory
3- wiggle a window on the remote display
4- watch the dedicated GPU memory rise by ~1GB/s for as long as the window is being wiggled on the remote display
The first time my computer mysteriously crashed from running out of memory was about a year ago. Whatever the issue might be, it isn’t a recent development.
I found DebugView’s log where SpaceView dumped its unpacked copy. No activity in there beyond the initial display connection chatter.
Since it is a VRAM-related issue, it is likely worth mentioning that I am using a GTX1050.
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.
On first install from spacedesk driver on my laptop I enabled mirror mode. Then I got a true mirror image with everything mirrored and text unreadable. I changed the resolution everywhere to same as first display 1366×768, but on the second iPad display image enlarged, the touchscreen doesn’t work, neither does the keyboard. I put everything back to the original resolution of the iPad 2048 x 1536, and image became normal, but the touchscreen and keyboard didn’t work. I created 3 walls and played with the settings from there but touchscreen doesn’t work either. I uninstalled spacedesk and everything was ok without configuring anything. Then I tried just changing the iPad display resolution to a lower 1152 x 864, but the image zoomed in again and the touchscreen didn’t work. Reinstalling again and I dare not open eiter the settings on app drivers or HTML5 as touchscreen and keyboard worked now.
In Task Manager, the amount of “Dedicated GPU Memory” reported as allocated to SpaceDesk keeps growing at a rate of about 100MB per screen update on the remote display. In the attached window capture, SpaceDesk has 19.4TB of hypothetical memory assigned to it so far, which is almost 1000X my total system memory. If I wiggle my mouse on the remote display, the allocation goes up by about 1GB/s.
I have to periodically restart SpaceDesk to forcibly free all of that ghost memory allocation since it will eventually cause my system to crash from running out of memory, presumably from tracking all of the meta-data for the stray allocations.
Anyone else seeing GPU dedicated memory creep up like this?
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.
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.
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/
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.
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.
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/.
I can’t figure out how to edit my post.
The tablet’s resolution is 1920×1200
Hi, I am trying to use SonarPen on my Android tablet (Fire HD 10) with spacedesk, however spacedesk keeps telling me that SonarPen is not connected even though I have calibrated it, enabled it in the client and plugged it in, and even when I redo those.
I can still use it for touch input but its pressure sensitivity will not be registered.
Connection method: Wi-Fi (I will try anything, but I don’t think networking is related to the problem)
Host specs:
OS: Windows 10 Professional 64-bit
CPU: Intel i5-4590 (Quad-core 3.7Ghz)
GPU: nvidia GTX 1050 Ti (4GB vram, monitor resolution 1920×1080)
RAM: 16 GB
Client specs:
OS: Fire OS 7 (Android 9)
CPU: Mediatek MT8183 Helio P60T (Octa-core 2.0Ghz)
GPU: Mali-G72 MP3 (?)
RAM: 2 GB
Hi,
the issue is still the same for me:
When I connect my (Android) Samsung Galaxy Tab S6 Lite with my Windows-PC and write something with my pen on the Tablet on the computers OneNote app, first the handwriting works for about 5s, then the computer screen freezes – the mouse can still be moved, but the screen remains freezed. Keyboard inputs do not seem to be recognised. Thus, I cannot provide the corresponding debug-file.
Please help!
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.
Hi @aquelemesmo,
Could you please try the methods suggested here
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.
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.
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.
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.
Hi @cyrex,
Did you click the “Uninstall” button?
If yes, please reboot your primary machine and check again.
