That seems good to know but counter to what was suspected by others. I'm still using Windows 10 and it's a shame that Win32 Disk Imager doesn't work with it because there have been times since I reported the problem in 2016 that I could have used it. I didn't turn off UAC when I used it on either Win 7 or Win 10. See my reply 2017-04-28.
---
** [tickets:#33] Windows 10 network drives not available**
**Status:** triaged
**Release:** 1.0
**Created:** Thu Mar 03, 2016 04:20 PM UTC by Jeff Ward
**Last Updated:** Fri Apr 24, 2020 07:13 AM UTC
**Owner:** Tobin Davis
The problem is with Windows 10(64bit) but the create ticket form "Windows Version" dropdown box only goes up to 8. The problem does not occur when using Windows 7(32bit) with the same conditions.
Upon running v0.9.5 as administrator, this message is shown:
File Error
An error occurred while querying the properties.
This usually means something is currently accessing the device; please close all applications and try again.
Error 50: The request is not supported.
Upon acknowledging the message, the app shows and can be used except that neither the network or mapped drives are shown or accessible when running in Windows 10. Otherwise, the app seems to function as expected. Images can be read from or written to a local drive. The app does not exhibit this problem when running in Windows 7 having the same network and mapped drives. The problem may be due to UAC. The "EnableLinkedConnections" registry modification does not fix the problem.
---
Sent from sourceforge.net because win...@li... is subscribed to https://sourceforge.net/p/win32diskimager/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/win32diskimager/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |