Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

My clipboard gets automatically erased from time to time.

For example:
I copy some text using Ctrl+C, and then paste it somewhere. And when I try to paste it again, nothing happens. I need to copy it once again.

This happens irregulary, sometimes I'm able to paste the text for many times, sometimes not even once.

I'm a developer, so I copy & paste very often (...), but this is really annoying.

How can I discover, which software does this? Is there any tool for monitoring WHICH PROCESS ERASED CLIPBOARD? Or if you experienced this problem with any software you've used, which one was that?

I'm using Windows 7, and many applications are running on my system, so it is hard to tell which one is causing all the trouble.

Update

Today I've confirmed that the misbehaving application is Visual C# 2010, and the problem is appearing only inside this application. I've tried to clipboard-monitoring tools as JRobert suggested. It seems that the text is correctly copied into the clipboard (so the clipboard history manager can record it) and then the Visual C# 2010 erases the clipboard content for some reason, which leads into "empty clipboard".

So thank you all, I'm now sure which application causes the trouble, and have even found Microsoft Connect bug tracker about this:
https://connect.microsoft.com/VisualStudio/feedback/details/554039/visual-studio-2010-clipboard-copy-and-cut-does-not-work?wa=wsignin1.0
And here is some additional info:
http://alpascual.com/post/copy-and-paste-problems-in-visual-studio-2010.aspx

Now I can just wait and pray for Microsoft to fix the bug.

share|improve this question
    
Might want to check out community.winsupersite.com/blogs/paul/archive/2010/05/06/… –  MrStatic Jul 3 '10 at 17:37
    
I've read the article and the whole discussion under it, but nobody experienced the same problem as me. :-( –  Paya Jul 3 '10 at 19:06
1  
You don't happen to be using KeePass do you? –  BloodPhilia Jul 3 '10 at 19:53
    
No I'm not, but I've installed it in the past, and uninstalled it... –  Paya Jul 3 '10 at 20:36
    
why you don't do it the easy way ? Start by closing the desktop applications you added before this issues comes up, I will start flash/AIR applications and desktop gadgets etc ... "too much is never too much" –  Revolter Jul 3 '10 at 21:19

4 Answers 4

up vote 2 down vote accepted
+50

Check out http://stackoverflow.com/questions/621577/clipboard-event-c

I don't think you can do more than there is available with the API, but this should be helpful enough to roll up your own Clipboard Monitor or request someone from that question to provide you theirs. Monitoring and showing the contents of the clipboard each time can be helpful whether to decide if something third-party is messing with your clipboard, from there you will have to identify the culprit by eliminating processes or something like that.

share|improve this answer
    
Yeah I already know it is possible to monitor clipboard changes, but I need to track it down to application, which made the change. And the problem doesn't repeat periodically, but randomly. So it would be very hard to trace the app by eliminating processes. –  Paya Jun 19 '10 at 20:07
    
Oh, I just got an idea that might help you to your solution. You could try to hook the API call (codeproject.com/kb/system/hooksys.aspx) and discover it in such way... –  Tom Wijsman Jun 19 '10 at 23:56
    
Yeah, this idea also crossed my mind, but it is a bit complicated to create such a program. I just hope there is also some other solution. –  Paya Jun 20 '10 at 10:43
    
Thank you for the reputation. :-) –  Tom Wijsman Jul 16 '10 at 0:53

An intermediate step (between selectively killing processes and hooking the clipboard API) might be one of these clipboard viewers. You might have to keep refreshing it manually hoping to discover when the clipboard cleared, but by narrowing that down, you might discover it happens, f/ex, right after some other apparently innocuous action you've taken.

share|improve this answer
    
It happens even if I don't taky any innocouous actions ... For example, I copy something into clipboard, and then start pressing Ctrl+V five times. It pastes 3 times, and then suddenly erases clipboard content, so the next 2 ctrl+v does nothing. And I just do the ctrl+v, nothing else. So I don't know how monitoring clipboard change will help me. –  Paya Jul 3 '10 at 19:16
    
And nothing user-related has taken place at that point? The phenomenon must be related to some process that is or isn't running at a given time, if it isn't reliably repeatable. My only other suggestion is to get a snapshot (f/ex, with Process Explorer) of the currently running processes taken at times when you can reproduce the phenomenon and at times when you can't. Then compare the two snapshots for their differences. –  JRobert Jul 3 '10 at 21:04
    
Well, it happens completely random, nothing user-related. However, I have now suspect Visual C# 2010 is causing the trouble, as I've googled it and it seems that others are experiencing similar (not the same) clipboard problems. Will investigate further. –  Paya Jul 4 '10 at 14:00

The clipboard in Windows has never worked very well. Long ago I gave up on it and started using freeware clipboard replacements. My latest favourite is ClipX (http://www.bluemars.org/clipx/). I just got tired of banging my head into Windows clipboard weirdness and limitations (the worst one being that you can only store one clip at a time).

Beyond that, you should be aware that Microsoft has done some very odd things to the Windows clipboard in some versions of Microsoft Office. I can't recall which versions of Office were the worst offenders in this regard, but I do know that after installing one of them, clipboard operation was seriously messed up until I disabled the related features. My recollection is that these problems occurred even when no Office applications were running. Anyway, if you haven't installed Office on the machine in question, obviously you should ignore this.

share|improve this answer
    
I haven't installed Office, so that shouldn't be the case. By the way, ClipX is clipboard history manager, not clipboard replacement. But it seems like the Visual C# 2010 is causing the clipboard weirdness, I'm trying to confirm that, but I'm currently unable to reproduce the problem. Will keep trying. –  Paya Jul 7 '10 at 15:47
    
You're splitting hairs. ClipX and (other tools like it) hook into the Windows clipboard and effectively remove all of its limitations, including the kind of strange behaviour you originally posted about. Why beat your head against the crappy default clipboard if you can work around it? –  boot13 Jul 8 '10 at 0:51

The proper way to do this, is to monitor API calls, Clipboard operations are function of user32.dll module

some of them are :

user32.dll!CloseClipboard
user32.dll!SetClipboardData
user32.dll!EmptyClipboard
user32.dll!GetClipboardData
...

some tools like Spy Studio or API Monitor let you track those calls and tell you who made them.

good luck !

share|improve this answer
    
Spy Studio has no 64 bit support, argh... But API Monitor seems to do so, will check it out later... +1 Looks awesome! Already have worked with XPerf but this seems to be more handy as it can show parameters and other stuff. :-) –  Tom Wijsman Jul 10 '10 at 14:21
    
The new version of API Monitor is nice, the only downside is that some thing are not very user efficient, like selecting multiple processes or filters... I'll report that one of these days. :-) –  Tom Wijsman Jul 16 '10 at 0:55
    
yeah they have just released the V2 :) looks promising. tell me if it give some results, and there is many others but most of them permit hooking over only one process (not very handy for your case) –  Revolter Jul 16 '10 at 19:44

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.