Jump to content
|Topic||Stats||Last action by|
|Windows 10: New leaked screenshots reveal brand new UI for Settings; death of Control Panel?||
|Microsoft to block Classic Shell in Windows 10: here is why||
|Massive car repair||
|The Big Wrestling Thread!||
|Slower boot speeds with "regular" HDD's connected||
Posted 13 June 2013 - 11:02
Posted 13 June 2013 - 12:03
Posted 14 June 2013 - 07:57
Same. It has to do with Explorer itself (I think), as sometimes I use TeraCopy to verify copies of data and even TeraCopy gets placed behind my current Windows Explorer window. At least TeraCopy remembers its position, so I just place it in a corner for it to be visible after a copy command. But still.
Aye I have the same issue. Using File Explorer (windows explorer), when I copy and paste a file, the transfer window is behind the active window that I initiated the transfer with. It's usually not a problem as it does it thin and I can see the progress on the taskbar.... unless I need to confirm permissions, then it'll just wait forever until i tab to the dialog box.
Posted 16 May 2014 - 11:20
sorry to bump but this problem is really annoying any one have a solution, sometimes ive missed a replace file dialog box because it's remained hidden and only after clicking the task bar picking the message up. I prefer my copy/move dialogs on top to get an idea of how they are doing.
Posted 19 May 2014 - 19:35
I'm also facing this issue. The only work-around I know - and it is temporary - is to close Google Chrome (exiting the little chrome logo on the notification pane near the clock as well), starting a file copy (with a big file, an .iso for example), open the copy/paste UI that shows up "hidden", cancel the operation and then, to check, pressing ctrl+v again to make sure the window pops up as it should.
Only then can I start Google Chrome again - and if I try to copy something, the file transfer UI shows on top as expected, until I restart the computer, and have to do this all over again.
It's VERY annoying and this bug really pisses me off, but I believe it is a Chrome-fault as it doesn't happen with any other browser.