Directory Freebies VS CheatSheet Forum

RSS

Email

Translate

Home About Archive Privacy Contact Advertise Guest Post

Last week a co worker of mine who wanted to remain anonymous, ran into the weirdest problem. She tried to use the “find in files” option in Visual Studio 2005 and even though the searched expression was out there in one of the files, she got the following result: “No files were found to look in. Find was stopped in progress.”

You can close Visual Studio, restart your computer or jump three times on one leg, but the problem remains. This is a very strange and odd bug, but fortunately there is a solution: press Ctrl+Scroll Lock and everything gets back to normal. If it doesn’t work, try to press Scroll Lock and than hit Ctrl+Scroll Lock again. I have no idea why or how it works, but the fact is that it does solve the problem, if anyone knows what happened here, please leave your comment and share your knowledge with us.

This is one of my shortest posts ever, but it might turn out to be very useful at harsh times…

Tags: , , , , , , ,
Top Ebook readers compared

6 Responses to “How To Solve: "No Files Were Found To Look In. Find Was Stopped In Progress"”


  1. Shankar Maru Said on Sep 4, 2008 :

    thanks man, I was having this problem for a while…..thanks a lot

  2. PHenry Said on Sep 4, 2008 :

    I too have ran SMACK head first into this problem too! And the CTRL+ScrollLock works (sometimes takes one or two smack backs to get it to convince VS to work properly but it does work). Why? I have NO idea neither but would be very interested to read WTF?

  3. tom Said on Sep 18, 2008 :

    My visual studio seems to crash when i do crtl+f :( no reason why

  4. Random Said on Nov 4, 2008 :

    Thanks! That did the trick. Oh Microsoft, thanks for this POS.

  5. Fer Fig Said on Nov 6, 2008 :

    Thanks! solved the “problem” for me too…
    This is weird one!!!

  6. J Said on Nov 10, 2008 :

    Funny, I’ve been using VS2005 for years now and never had this problem… until just a few minutes ago! Luckily a quick question to Dr. Google pointed me to the answer here (and to a couple of dozen other sites!) Curious that the “problem” has been around since at least 2005 and yet nobody has yet been able to say *why* it happens…

Post a Comment