I've got my Kronos2 73 (OS 3.1.2) connected via USB to my Windows 10 64-bit desktop PC. The install of the Korg drivers and the USB/MIDI drivers went fine, as did the install of the editor. I can see the Kronos in Device Manager and when I use either the 'Configure Korg Driver Setup Utility' or 'Configure KORG USB MIDI Driver' in the Korg startup folder, everything seems correct (no error messages). I've got Enable Exclusive active on the Kronos in the MIDI global tab. However, whenever I start the editor (version 3.1), I get the splash screen and I can see the empty editor screen behind the splash screen but that's as far as it goes. I then get a Windows dialog box that says MIDI Quest 11 / Pro / Essentials / UQ has stopped working and I have to close out.
Any ideas why it won't start or possible conflicts? I've tried uninstalling and reinstalling the Korg drivers, the MIDI drivers and the editor, including unchecking the "uninstall Korg devices only" box on uninstall to remove any conflicting devices with no success.
Kronos Editor 3.1 crashes on startup
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
- Posts: 15
- Joined: Mon Mar 06, 2017 12:46 am
- Location: Western MA
-
- Junior Member
- Posts: 82
- Joined: Wed Oct 22, 2014 5:33 pm
- Location: UK
I got the exact same error last night after a clean Windows 10 re-build and mine too was all working before. I tried various options to fix, in the end I did a right click on the Editor icon and selected the "troubleshoot compatibility" this suggested some settings that I accepted and it is now running in windows 8 compatibility mode, so give that a try to see if it helps.
I suspect one of the latest Windows updates has upset something so hopefully there will be a better fix later
Steve
I suspect one of the latest Windows updates has upset something so hopefully there will be a better fix later
Steve
Korg Kronos2-61
My Editor is now working as well
Thanks a million for the compatibility tip, I spent a considerable amount of time trying to get the editor working, and didn't even think of the compatibility setting.
All good now,
Thanks again
All good now,
Thanks again
There have been compatibility issues as well as OS issues with the editor. Did you download the driver as well? You can find it on the support pages.
Try searching the forums (use Google) and you might feel me some answers. I run 8.1 and it works but it can become unstable. This is one of those things yet to be resolved by KORG.
Let us know.
Try searching the forums (use Google) and you might feel me some answers. I run 8.1 and it works but it can become unstable. This is one of those things yet to be resolved by KORG.
Let us know.
-
- Junior Member
- Posts: 82
- Joined: Wed Oct 22, 2014 5:33 pm
- Location: UK
Editor crashes
Yes latest drivers used. It was working before under Windows 10 so I suspect a later windows update has knocked it out of skew
Korg Kronos2-61
-
- Posts: 15
- Joined: Mon Mar 06, 2017 12:46 am
- Location: Western MA
Thanks for the tip--I will give that a try.MrSteveVee wrote:I got the exact same error last night after a clean Windows 10 re-build and mine too was all working before. I tried various options to fix, in the end I did a right click on the Editor icon and selected the "troubleshoot compatibility" this suggested some settings that I accepted and it is now running in windows 8 compatibility mode, so give that a try to see if it helps.
I suspect one of the latest Windows updates has upset something so hopefully there will be a better fix later
Steve
Matt
-
- Posts: 15
- Joined: Mon Mar 06, 2017 12:46 am
- Location: Western MA
Success! Steve was 100% correct.....this appears to be an incompatibility with the latest build of Windows 10 64-bit (and possibly 32-bit). I did as he suggested, selected the "Troubleshoot Compatibility" option from the right-click menu on the icon in Explorer, and let it do its thing. The first thing it tried was Windows 8 compatibility mode and that worked perfectly.
Thanks for the tip. Hopefully others having this trouble will search and find this thread.
Thanks for the tip. Hopefully others having this trouble will search and find this thread.