Just maybe, I've out-fumbled this one. While I was having a problem trying to use a right-click to select "delete" for deleting a group of items that had been chosen using "select all", I went into Task Manager - Details to check on the process "explorer.exe" and I found it had a Process ID of "340".
That number "340" has been associated in the past with error codes related to the process "csrss.exe" which is the client server runtime subsystem for the main Windows32 processes. If you look in Task Manager and find you have two of these same processes, and you check their "Properties" and find both show a legitimate Microsoft digital signature, and you wonder why there are two of them, the answer is that one is for "all users" and the other is for you as a user. Malware has been known to use this process name to hide on a system, but if both of these are signed by Microsoft, and both are located in "Windows\system32" then you're OK, and you can quit worrying.
But I'm digressing. If your "explorer.exe" in Task Manager is not showing a Process ID number with four digits, (such as "3840") right-click on it and then select "end process" and then do a reboot of your computer. You'll have to initiate that using "Ctrl-Alt-Del" or by shutting it down with the main power switch, because once you "end process" for "explorer.exe" your desktop will go blank. Once you do the reboot, check again for the Process ID of "explorer.exe" and it should show a new PID number with four digits, and your problem with the right-click crashes should be solved.
This probably is caused by something hanging during a shutdown, or during an incorrect shutdown, when not everything got terminated correctly before the power was cut off. That's my theory anyway...
.png)
.png)
For me, explorer.exe, has a 4 digit process ID. I have 3 copies of crss, all by Microsoft.
ReplyDeleteMy problem continues. UGH!!!
The recommended "cure" is to install the freebie "ShellexView"
ReplyDeleteand then one-by-one disable all the non-Microsoft items until you find the culprit, but that didn't help me at all. So I'm suspecting it's a Windows item that's hanging it up, but I didn't find it with ShellexView, because the list is long, and I'm the impatient type.