AceInfinity
Emeritus, Contributor
I've noticed a few bugs since I've been using Windows 10 as my main OS so far, and I've already submitted these to the feedback center. I'd like to post them here to not only validate my observations, but to make others aware of the bugs that I've found.
1. With my laptop outputing video from the HDMI port to a second monitor, if I move a window over to the second monitor, then unplug the HDMI cable, the extended display disappears (as it should), the window from my extended display gets placed onto my main display, but when the desktop view is refreshed, the taskbar seems to be misplaced below the viewable area of my screen. There's no way to get it back even if I plug the HDMI back in, I physically need to reboot my laptop/PC.
2. Windows Libraries -- I've noticed an issue with Library locations being opened in explorer by other programs causes an invalid path to be constructed. For instance, when I open a project in Visual Studio from a library location which should resolve to "C:\... some path ...\Projects", what happens is that explorer tries to open "C:\... some path ...\Projects\Projects" instead. I've also noticed the same thing with creating a taskbar toolbar to a library location; double click on a folder from that toolbar, and it will open an invalid path in explorer.
* I actually think now that I've been fooling around a bit that this is the reason why some of my file copy/move operations were failing... Who knows.
1. With my laptop outputing video from the HDMI port to a second monitor, if I move a window over to the second monitor, then unplug the HDMI cable, the extended display disappears (as it should), the window from my extended display gets placed onto my main display, but when the desktop view is refreshed, the taskbar seems to be misplaced below the viewable area of my screen. There's no way to get it back even if I plug the HDMI back in, I physically need to reboot my laptop/PC.
2. Windows Libraries -- I've noticed an issue with Library locations being opened in explorer by other programs causes an invalid path to be constructed. For instance, when I open a project in Visual Studio from a library location which should resolve to "C:\... some path ...\Projects", what happens is that explorer tries to open "C:\... some path ...\Projects\Projects" instead. I've also noticed the same thing with creating a taskbar toolbar to a library location; double click on a folder from that toolbar, and it will open an invalid path in explorer.
* I actually think now that I've been fooling around a bit that this is the reason why some of my file copy/move operations were failing... Who knows.
Last edited: