Windows 10: Not able to drag tabs or files after computer is on for a while

Hello,
I've been dealing with this problem for about a year now. Once my computer's been on for a bit, it suddenly stops letting me click and drag tabs and files on the desktop and file explorer. Doesn't matter if I've been using it or just left it sitting there. Oddly, I can still click and drag windows around. A restart fixes it, but nothing else I've tried, like reinstalling mouse and computer drivers, works. Currently on the latest version of Windows 10. Any idea what's causing this?
Thanks

submitted by /u/EpicGamerRosander
[link] [comments]

:)

 

Drag and Drop

Hi Charles,

the steps you suggested didn't work for me but, when pressing the escape key it somehow expanded the drive and by using drag and drop to the single file in the list worked.

In the past I could drag and drop multiple folders onto the drive on the network computer(s). Doing it on individual folders will take far too long and time consuming and is not an option.

Microsoft should be able to identify what is blocking it and issue a fix.

My machine is multi boot so tomorrow I will try with Windows 7.

Many thanks for your help,

Deric

 

Burning Files To cdr

I tried to drag a .txt file to the burn list, as suggested above, but it will not drop in. I get a message "+add to burn list" but I cannot get it to drop into the burn list. Is there another step I am missing?

 

Drag and drop files, I am not able to drag files from the files window to folders in the navigation pane.

• I am able to do the same using other computers with Windows 10.
• If I drag and drop to other file explorer windows, the file(s) copy or move as expected as long as I don't try to drop them on a folder in a navigation pane.
• I do not get any error messages.

I get the following when sfc completes:

Windows Resource Protection found corrupt files but was unable to fix some

of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For

example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not

supported in offline servicing scenarios.