Without a crash report there is nothing i can do about this issue…
Not at my home computer right now but will see how to generate a crash report.
I’m not having good luck either… Tried to install it on another PC and run it. Program launches, splash screen appears, it (Launcher.exe) briefly appears in Task Manager, then “poof”. Uninstalled it, removed any leftovers (including config data, probably from an older version), and it launches but with “Error: Invalid class”.
I’m able to configure it though but again, no flash drive appears in the drop-down list. Refreshing it causes “Error: Invalid class” again. Same behavior that I’m seeing on my home computer but different error message.
Please try the latest alpha, if the issue still persists then i will investigate further. https://cyanlabs.net/api/ci/Syn3updater/latest/download
Latest build behaves exactly the same. Oddly, it gives the same “Invalid class” message on the one computer (same as the stable build) and “Object reference not set to an instance of an object” on the other computer. It behaves differently on two different machines.
It doesn’t seem like many others are running into this though so I can understand if there’s little you can do, without knowing what to look for without crash reports. How do I get a crash report to send to help ? I can certainly try.
Saying “latest build” without saying what the version number is doesn’t help a whole lot, i also forgot to mention you need to change the branch in the settings to be “Alpha” instead of “Stable”
I have the logs of what just failed.
UNique ID 1ebe0c55-8d70-606e-9b55-0242ac120005
System.IO.IOException
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
10054
System.Net.Sockets.SocketException
An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state)
at System.Net.Sockets.NetworkStream.BeginRead(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
0
8
BeginReceive
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Net.Sockets.Socket
System.IAsyncResult BeginReceive(Byte[], Int32, Int32, System.Net.Sockets.SocketFlags, System.AsyncCallback, System.Object)
-2147467259
System
at System.Net.ConnectStream.EndRead(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncTrimPromise1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization)
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClientHandler.WebExceptionWrapperStream.d__4.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Cyanlabs.Syn3Updater.Helper.FileHelper.d__8.MoveNext() in C:\Users\Scott\Documents\GitHub\Syn3Updater\Syn3Updater\Helper\FileHelper.cs:line 317
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Cyanlabs.Syn3Updater.Helper.FileHelper.d__6.MoveNext() in C:\Users\Scott\Documents\GitHub\Syn3Updater\Syn3Updater\Helper\FileHelper.cs:line 262
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Cyanlabs.Syn3Updater.UI.Tabs.DownloadViewModel.d__67.MoveNext() in C:\Users\Scott\Documents\GitHub\Syn3Updater\Syn3Updater\UI\Tabs\DownloadViewModel.cs:line 304
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Cyanlabs.Syn3Updater.UI.Tabs.DownloadViewModel.d__66.MoveNext() in C:\Users\Scott\Documents\GitHub\Syn3Updater\Syn3Updater\UI\Tabs\DownloadViewModel.cs:line 178
0
8
EndRead
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Net.ConnectStream
Int32 EndRead(System.IAsyncResult)
-2146232800
System
You gave me a link to your “latest build”.
I’ve since changed it to “Alpha”, it downloaded and updated files, then I deleted the configuration folder and restarted. On this machine, I continue to get the “Invalid class” error and no USB drives appear in the list.
My “Logs” folder is empty. More than happy to enable logging to help sort this but I don’t know how, sorry… There is an “applog.txt” file but it doesn’t look like it’s applicable for this issue.
When you are in Windows side of bootcamp, can you access or write to a USB? This was the same issue I had with Parallels permissions. It just happened one day, but was related to a Windows update that reset permissions. Just sharing.
I’m on the machine running Parallels at the moment. I can format the flash drive using File Explorer. I opened a PDF in Adobe Reader and saved it to the flash drive. I just exported data from UPS Worldship to the flash drive. Those two random programs are not built-in Windows programs that might be able to override some permissions.
I’m open to trying different things. Let me know !
1 Like
Just info…
When I use the app in Parallels, I have to insert the USB and map to the VM first before I launch Syn3 Updater. If the app is open before I insert the USB, Syn3 Updater will not see it even after refreshing the app. I have to quit the app and relaunch to see the usb connected to the VM. There are no error messgaes, it’s just like the app sees a snapshot of the disk structure when it starts and does not refresh that snapshot, or is not presented with updated info from Parallels/Windows.
I only see this behaviour in Parallels VM with Win 10 (latest version 21H1). There are no issues on my desktop Win 10 machine or Surface Pro 3.
Here are 2 threads that kind of talk about this, but for specific hardware not usb in general.
Mac OS Big Sur/parallels 16.1.1: don’t connect usb external devices | Parallels Forums
USB devices other than storage should be also mountable in paralles desktop | Parallels Forums
Already ahead of you 
At least on the mapping part. The flash drive is only “seen” by Windows (the VM in this case), not on the macOS side at all. I want to say I put the flash drive in first, before launching Syn3, but I’ll try again.
Okay, just confirming, on a previous try when Parallels asked me what to do with this particular flash drive (it remembers it too), I told it connect it to Windows, not macOS, and I must have selected “remember” or “don’t ask again”. Under Devices, USB & Bluetooth, the flash drive I’m trying to use is checked for use.
Running Syn3 Updater, no change. Clicking the refresh button is what triggers the “Invalid class” button, by the way.
I just did an experiment with the Parallels. This is (in my case) a Parallels issue, without doubt. Parallels seems to be pretty flaky with USB assignments.
What I did:
Shut down Parallels completely.
Remove any USB devices from the computer.
Navigate to /Library/Preferences/Parallels/
Make a backup copy of dispatcher.desktop.xml
Delete this file from the /Library/Preferences/Parallels directory.
Start Parallels. You will not be able to see a VM. Don’t worry yet…
Quit Parallels completely.
You will notice the new dispatcher.desktop.xml is smaller and does not contain USB devices.
Start Parallels again, it will prompt you to install Windows. At the left bottom of the window is an “OPEN” button. Select and it should have the VM listed. Select and open.
This completely solved the issue I was having with selecting a USB device.
WARNING: This will erase all USB devices listed for the VM, so they will all be new connections.
This will also make a new alias for the VM. I deleted the old one just to clean up.
I played around with making one of my USB’s a permanent assignment to Parallels VM. This works with no issues. Syn3 Updater sees it instantly. Might be the way to go…
The link is always latest version, so as i don’t know when you ran it that doesn’t mean a whole lot to me…
Honestly if you are not using it on native windows then i am not interested in any crash logs or bug reports.
It’s unclear at this point if you are using bootcamp or using virtualization.
you also seem to be going out of your way to not tell me versions numbers. “Latest” doesn’t mean much when there was 5 alpha builds built yesterday
I have both. I’m back in Boot Camp now and happy to say it now works. Build in title bar says “2.9.7.11 (Alpha)”. I tried multiple times yesterday in the Alpha channel so I presume I could have been running any of yesterday’s (5) builds at different times…
3 Likes
Then the issue was to do with a drive either being encrypted or drive with no readable filesystem as that’s the only fix implemented.
Glad it’s working now 
1 Like
2.10.0 Released - please only report issues if you are on this version or newer!
1 Like
May be obvious, but change your branch to Stable if you had changed it in the past to Alpha or Beta