Google’s Quick Share app for Windows updated, removes desktop shortcut

Google is rolling out an update to Quick Share for Windows which fixes a handful of issues, improves performance, and strangely removes the desktop shortcut.

Version 1.0.1939.4 of Quick Share for Windows was released this week, as details on Google’s changelog. The update delivers several bug fixes including crashing issues, an issue that caused the PIN to be required even if you are exchanging between mutual contacts, and an issue that would cause transfers to fail if they took longer than a minute.

Strangely, this update to Quick Share for Windows also removes the desktop shortcut for the app as soon as it is installed. You can still manually recreate the shortcut through File Explorer, but Google has removed the one that is put in place on installation.

The full changelog reads:

• Fixed an issue that caused the app to crash when you open your files and folders.
• Fixed an issue that caused the app to crash when you close it.
• Removed the Quick Share desktop shortcut.
• Fixed an issue that caused transfers that took more than a minute to time out.
• Fixed an issue that shows the PIN code when both the sender and receiver are mutual contacts.
• Added car and foldable devices to the list of device types.
• Improved app animations for better system performance and longer battery life.
• Added credential expiration and revocation handling, so you’ll be notified more often when the app is not working properly.

Another oddity here is the mention of “car” in new device types, as the Android Automotive platform does not yet support Quick Share (and it’s hard to imagine where that might be especially useful).

Google also says to expect better performance and “longer battery life” thanks to improved animations within Quick Share. Improvements on both accounts are likely minimal, but it’s a welcome update nonetheless.

This update still does not support ARM-powered Windows machines such as those powered by Snapdragon X Elite.

More on Quick Share:

Follow Ben: Twitter/X, Threads, and Instagram