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
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?
[quote who="sdRohan" reply="13" id="3786379"] I would like to have you try another (PITA) process as we really need to see if anything new in 3.5 (just released) is the cause. We did not change anything for KVM for 3.5 but we have to be certain. Again, this is not a fun process, we are sorry for it, but it would be a purge on each PC, reboot, and an install of this 3.44 build: Purge: ht
The Primary is Version 1909 (OS Build 18363.657). The Secondary is Version 1909 (OS Build 18363.959). Yes, the Clean Boot is arduous, and not at all like the Shift-F8 process of yesteryear. My Secondary is in a Clean Boot state, with a new Admin-level account, no dependencies, and no firewall (still remains that way even now, no reason to put it back yet). My Primary is my main development machine, and Clean Boot into a separate new Admin-level account proved
Video of me trying to connect from Primary to Secondary: https://www.dropbox.com/s/n5ty6rkvrjojeim/Multiplicity-2020-08-17-15-09.wmv Does it help to know that the Primary has 3 monitors, two DVI on an external video card, and one via a DVI-to-USB adapter? I also have Fences 3 installed, which had crashed when I recorded the video, but the results were identical to previous runs (so,
I turned on the Logging to the Event Log on the secondary, and although I see some other Informational stuff in the Application Log, the only one I see directly relating to Multiplicity is: The description for Event ID 257 from source Multiplicity cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another
Secondary has 2 video ports on the motherboard only: HDMI and DisplayPort (using HDMI). I could try capturing video of the process. For some reason the Secondary is currently unresponsive, I will check it out after I reboot it. Primary is reporting two errors in the Application Event Log: Faulting application name: MPRDP64.exe, version: 3.0.90.0, time stamp: 0x59760b1d Faulting module name: KERNELBASE.dll, version: 10.0.18362.628,
Follow-up: 2) If you disable the firewalls on each PC, does that have an effect? -- No change. Turned off the Windows Defender firewall from both machines, and it still did not connect in KVM mode. 5) If you try the opposite, make the Secondary a Primary, reversion the current Primary, can you connect to it? -- No. If I make Primary into Secondary (and remove the
Thanks, Sean, I'll try to answer these in order: 1) Has it ever worked to KVM connect tot he PC in question? -- No, this is a new purchase, and this is the only time these two computers have ever communicated via Multiplicity 2) If you disable the firewalls on each PC, does that have an effect? -- Good question, I'll have to look at what firewalls each PC, but to
Additional note: I can connect using Seamless, and that works correctly, but I really need this second computer to be in KVM mode. If I hastily click on the Gear icon at the top of the connection screen, I get the notification "Successful connection Multiplicity has connected to ( ) using AES-256 encryption Stardock Multiplicity 3", but still no screen appears to control the second computer.
I followed the Connection Issues 101 thread, all the way to running the Purge_MP-New on both machines, and reinstalling, using exactly the same download. Installed the second machine first, as a Secondary, then the primary machine, as Primary. Primary confirms that it can see Secondary, *but* when I try to connect, I get the "Connecting to . . . . . . [ Cancel connection ]" window for maybe 5 seconds, then it just goes away. What else can I do to troublesho