I have the same issue. The difference is my error message says:
"The drive or network connection that the shortcut '' refers to is unavailable.
Make sure that the disk is properly inserted or the network resource is available, and try again"
So the shortcut is blank in my case! ... it keeps re-appearing
One more thing. Having this popup I am not able to open "Preferences" from the menu.
I think it will not open once you have a popup from the system hanging.
It's not our code that's doing it...we never asked for this behavior - but we're ultimately responsible for this, obviously
there's a bug filed on it, we're working on it - but not sure it will be fixed for 18.4
the best workaround at the moment is to put all of your broken desktop links into a folder - that will 'hide' the problem
I also have this problem. I get the comment about the empty shortcut rather than a named one. It persists even if I delete all my shortcuts on the desktop (where I do not have any for non-existent shares anyway).
I have the same issue exactly.
I do not have shortcuts on the desktop at all but empty shortcut message keeps popping up.
I found the issue in my case.
There was a mapped folder to WebDAV which is not working under "My Computer".
Removing that link fixed the issue.
It's a Java bug
According to this JDK bug , the issue was introduced in jdk1.8.0_191 and will be fixed in 1.8.0_211, 11.0.3-oracle, and 12b23.
.SQLDeveloper 18.3 with jdk shipped (and 18.4 will ship) with jdk1.8.0_181 which works fine. For users who have installed 18.3 and specified the jdk,
they need to modify /Users//AppData/Roaming/sqldeveloper/18.3.0/product.conf to comment out (or remove) any SetJavaHome declaration and install the bundled version (or reference their own 1.8.0_181 installation)[
I'm not a professional computer user, but it sounds weird why java (or SQL developer) scans my desktop shortcuts.
Moreover not only scans but try to do something with the linked file, at least checks if it exists or not. For what purpose?
I had the same questions, but like I said, that's not our code, it's core Java bits. Which were identified as a bug. And has already been fixed as noted above.