Additional info, If I blindly type {Winkey-L} in the black KVM window, the secondary Desktop locks and shows the lock screen. I can mouse click and enter my password and it logs in and displays a black screen again.

Some display adapters will not display anything unless a monitor is physically attached.

There are hdmi dummy plugs you can buy to deal with this issue.

Unfortunately combined Nvidia plus intel graphics systems are something of a hack which can cause issues as applications may be assigned to the wrong display adapter.  In the past they have broken the use of DirectWrite text rendering due to poor drivers.

If you get a blank screen it is likely the wrong adapter is being captured.  You may be able to force multiplv64.exe to use one of the adapters via your Nvidia software.

Thanks, not sure how to force the adapter. My Desktop does have an Nvidia adapter.

Does the laptop have two graphics adapters (check Windows Device Manager)?  If it does, see if the laptop has a BIOS setting that locks it into a single either one of them.  If it does, set it to use just one of them and I suspect the laptop will behave itself.

Just one adapter on the Primary Laptop.

Have the same problem as OP, the purging and installing of the older version (3.44) helped, I now can use KVM again. I only had to do the procedure on the primary computer, the secondary still runs with 3.5.

Hopefully you find the problem soon, so that I can update.

Please review this post.  There is a file there we need you to try:

https://forums.stardock.com/501231/get;3787066

Sean Drohan
Stardock Support Manager

Sorry, I misunderstood that the laptop was the secondary machine.   In any case, the question about two graphics adapters concerned the secondary machine, whatever it is. 

That said, might the secondary machine be turning off its graphics adapter when there is no monitor attached?   It seems pretty clear that MP connects through the secondary machine's graphics adapter(s) [as distinct from RDP which ignores the remote machine's graphics adapter(s)].

This is correct.

I think ejv's issue has been confused with yours.  Some graphics cards (AMD I think) require a physical monitor attached or capture apis fail on it.  This can be worked around using HDMI dummy plugs.

Super cheap and equally effective:

https://www.amazon.com/s?k=hdmi+dummy+plug&crid=24SEVXR93XQ2U&sprefix=hdmi+dummy%2Caps%2C524&ref=nb_sb_ss_ts-ap-p_1_10

Sean Drohan
Stardock Support Manager

It's been a very busy week, and I didn't have time at the moment to go through a PITA process, but I do now.  Hopefully I can un-hijack this thread while I'm at it

Yes, purging Multiplicity 3.5 and installing 3.44 does indeed correct the issue.  What can I tell you about my primary and secondary computers that will help the dev team to modify 3.5 such that upgrading won't hoop the process?  For now, I'm happy sitting at 3.44, but I'm sure the time will come that I won't be.

Looking at other posts, you may want to know the hardware details of my secondary.  It is an AMD Ryzen 5 2400G with 1 socket, 4 cores and 8 logical processors.  It also has virtualization enabled with Hyper-V installed, because this was the intended purpose of the box (to install and isolate different client environments so that they don't impact my main dev machine).  It's a moderately new and very capable box.

UPDATE: I got a dummy DVI-D plug and it fixed the problem.

Thanks...

Works every time 👍

Thank you for reporting back.

Sean Drohan
Stardock Support Manager

Are you able to find the dmp data files that the event log referenced?  

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MPRDP64.exe_56b2263f5c7827f0a31e19d7c55cac29ed717cf_44d5ae03_42dd6c95-f0e5-48a1-b89e-8c4cc212d44a

With that we should be able to learn more about the issue and hopefully resolve it quickly.

If not are you willing to reinstall 3.5 on the primary, make it crash again (I believe it only has to be the primary moved to 3.5) and then find the files that a new event log entry will reference and send those to us.

Yes, I still have that folder, and the Report.wer file that is in there.  Can I attach files to forum posts, or should I e-mail the file to someone?

It's actually not that big of a file (because I don't allow MS to collect Full telemetry):

Version=1
EventType=APPCRASH
EventTime=132421697719175264
ReportType=2
Consent=1
UploadTime=132421697724005257
ReportStatus=268435456
ReportIdentifier=42dd6c95-f0e5-48a1-b89e-8c4cc212d44a
IntegratorReportIdentifier=86f7e310-7ca8-455c-98c1-1c88abde42b8
Wow64Host=34404
NsAppName=MPRDP64.exe
OriginalFilename=MPRDP.EXE
AppSessionGuid=00001128-0001-000c-8961-931cd574d601
TargetAppId=W:00005626016e4a0bf4d77b407604f67a417e0000ffff!0000e48da799c7f970e4ec4dc5d919f0b10cfc038b98!MPRDP64.exe
TargetAppVer=2017//07//24:14:58:37!196911!MPRDP64.exe
BootId=4294967295
ServiceSplit=33554434
TargetAsId=924
UserImpactVector=3146544
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=0f9828d258ae9d97716c923ec5e731fd
Response.BucketTable=4
Response.LegacyBucketId=1255539194435416573
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=MPRDP64.exe
Sig[1].Name=Application Version
Sig[1].Value=3.0.90.0
Sig[2].Name=Application Timestamp
Sig[2].Value=59760b1d
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.18362.628
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=f96f12ee
Sig[6].Name=Exception Code
Sig[6].Value=c06d007e
Sig[7].Name=Exception Offset
Sig[7].Value=000000000003a839
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18363.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=cca6
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=cca680a2a47b305a5033ac7e35643d18
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=2706
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=270658d123f3bbd5da180052d438546a
UI[2]=C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.exe
LoadedModule[0]=C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[5]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[6]=C:\WINDOWS\System32\ole32.dll
LoadedModule[7]=C:\WINDOWS\System32\combase.dll
LoadedModule[8]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[9]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[10]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[11]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[12]=C:\WINDOWS\System32\sechost.dll
LoadedModule[13]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[14]=C:\WINDOWS\System32\win32u.dll
LoadedModule[15]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[17]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[18]=C:\WINDOWS\System32\USER32.dll
LoadedModule[19]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[20]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[21]=C:\WINDOWS\System32\shcore.dll
LoadedModule[22]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[23]=C:\WINDOWS\System32\profapi.dll
LoadedModule[24]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[25]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[26]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[27]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[29]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\winmmbase.dll
LoadedModule[31]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[32]=C:\WINDOWS\SYSTEM32\DWRITE.DLL
LoadedModule[33]=C:\WINDOWS\SYSTEM32\d2d1.dll
LoadedModule[34]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[38]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[40]=C:\WINDOWS\System32\crypt32.dll
LoadedModule[41]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[42]=C:\WINDOWS\System32\WINTRUST.DLL
LoadedModule[43]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[44]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[45]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[47]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvwgf2umx.dll
LoadedModule[48]=C:\WINDOWS\system32\nvspcap64.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\ColorAdapterClient.dll
LoadedModule[53]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[54]=C:\WINDOWS\SYSTEM32\icm32.dll
LoadedModule[55]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.657_none_17b0a85e6da0b266\gdiplus.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[57]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[58]=C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[60]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.657_none_e6c5b579130e3898\comctl32.DLL
LoadedModule[61]=C:\WINDOWS\System32\TextInputFramework.dll
LoadedModule[62]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[63]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[65]=C:\WINDOWS\System32\iertutil.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\gpapi.dll
LoadedModule[67]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[68]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[69]=C:\WINDOWS\System32\mswsock.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[71]=C:\WINDOWS\System32\NSI.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[73]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[74]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[75]=C:\WINDOWS\system32\wshbth.dll
LoadedModule[76]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[77]=C:\Windows\System32\rasadhlp.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[80]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvd3dumx.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18363
OsInfo[3].Key=ubr
OsInfo[3].Value=657
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=1
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=548194
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.657.18362.0-11.0.175
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16355
OsInfo[19].Key=svolsz
OsInfo[19].Value=953
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.657.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=2DBEA21E-0A44-4747-A2EE-416EECF243AD.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Multiplicity remote control
AppPath=C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=617BF6C8879012B01D920A3CF8D73B00
MetadataHash=479157658

Are you familiar with, and comfortable using, WinDBG?
https://cdn.stardock.us/support/uploads/windbg_x64.exe

Since it seemingly crashes too quickly to attach it to a running process (MPRDP64.exe), registering it at the default debugger might be necessary (can be undone).

The process to do so with the standalone exe (above):

From an elevated command prompt: <path to WinDBG_x64.exe>\WinDBG_64.exe -I
The capital 'I' is important.

So if you had it on your desktop, it would look like:

C:\Users\<yourWindowsAccountName>\Desktop>windbg_x64.exe -I

You would get this if successful:

Here is how you can unregister WinDBG after:

https://stackoverflow.com/questions/1014345/how-do-i-stop-windbg-from-being-the-interactive-debugger

There is a Windows store version of WinDBG as well:
https://www.microsoft.com/en-us/p/windbg-preview/9pgjgd53tn86?activetab=pivot:overviewtab

Its has the convenience of being easy to enable \ disable it as the default debugger:

With either registered, initiate a KVM connection, should crash and pop the debugger.

When it crashes, for the WinDBG.exe, there is a command-line where you can type:

.dump /m <path to where you want the dump>\MPKVM.dmp

For the Windows store one, the same syntax done, just not as familiar with where it is typed.

You can upload that to a cloud drive service and post a shared link here.  If you are not comfortable with that, you can PM me a link.

Thank you for your help here, Vaneyen.

Sean Drohan
Stardock Support Manager

I can confirm seeing issues with the APP crashing (ERROR FROM EVENTVWR BELOW)

I have 3.5 build 00096 on 3 machines which works perfectly, but on my new windows 10 machine I added today won't connect but crashes the same way mentioned here, but if I install version 3.44 build 00090 the KVM works.

So looking very much for a solution to this.

######################################################################################################

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: MPRDP64.exe

P2: 3.0.90.0

P3: 59760b1d

P4: KERNELBASE.dll

P5: 10.0.19041.488

P6: 5b4a3325

P7: c06d007e

P8: 0000000000023e49

P9: 

P10: 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD502.tmp.WERInternalMetadata.xml

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_MPRDP64.exe_6c75d43dd833f12d60af0a8a1205e73583174e3_44d5ae03_f1191741-449d-4639-8ff3-c35d24ff6e9f

Analysis symbol: 

Rechecking for solution: 0

Report Id: a1e5c4a5-b2ff-4188-9a3a-ee4aa901c028

Report Status: 100

Hashed bucket: 

Cab Guid: 0

If anyone who is experiencing the issue with MPRDP64.exe crashing out when connecting to a remote machine (not a black screen issue, an actual crash) is willing to try what Sean suggests in Post 43 we would be most grateful as we want to address this issue but none of our computers is showing any problems with KVM mode which makes it hard without additional information.

Whats in the event log only shows the end point of the crash which is a windows dll, it doesn't tell us what called it which is the important thing.

Started to run the process of post 43, did this by upgrading from 3.44 to 3.5 build 00096 and registered the debug. I then went to replicate connecting and it all worked! No crashing, so what ever installing 3.44 first then upgrading seemed to resolve the issue.

Please go here:

\ProgramData\Stardock\Multiplicity 

That is ProgramData, not ProgramFiles - you may need to unhide that folder as it is hidden by default.

Delete the license.sig, open the MP UI, it will prompt you to activate - do so, try to KVM connect, does it crash?

If so, let us know.  If not, please purge on each box:

https://forums.stardock.com/486104/multiplicity-support-faq#reinstalling

and reinstall 3.5 ONLY. Let us know if it crashes and with a dump if so.

Thank you for the time and effort.

Sean Drohan
Stardock Support Manager

All,

Is there anyone here that is getting the crash able to perform the tests detailed in:

https://forums.stardock.com/501231/get;3788076

https://forums.stardock.com/501231/get;3788444

We would really like to get help in resolving this.

Thanks,,
Sean Drohan
Stardock Support Manager

I will attempt to get what you need, I fully understand you need the logs. Just solving one thing at a time here.

Excellent, thank you.

Sean Drohan
Stardock Support Manager