Find in Files doesn't show its results - by mikeidge

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 836028 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/18/2014 4:25:54 AM
Access Restriction Public


When I search for something across the solution or project in VS2013, I get confirmation that VS2013 has indeed found what I'm searching for, but it's not telling me where those instances are. This used to work OK in VS2010.

Here's some example output in the Find Results window:

Find all "banana", Subfolders, Find Results 1, Entire Solution, "*.c;*.cpp;*.cxx;*.cc;*.tli;*.tlh;*.h;*.hh;*.hpp;*.hxx;*.hh;*.inl;*.rc;*.resx;*.idl;*.asm;*.inc"
  Matching lines: 5    Matching files: 4    Total files searched: 3710

So, there are five matching lines which VS has found, but the search is somewhat useless as I have no idea where they are, which I'd have thought is pretty much the whole point of a search feature! Is there a new option I'm unaware of that is exhibiting this daft behaviour, or is Find borked in VS2013?
Sign in to post a comment.
Posted by Mark [MSFT] on 5/8/2014 at 5:39 PM
We are resolving this issue as "Wont Fix" because a reliable workaround exists (see below).

We believe the issue is being caused by another software installation interfering with an important registry key, but have not yet isolated the offending installer and would appreciate the community's input to isolate that by letting us know about software installed right before you start seeing this issue.

If you are experiencing the problem you can fix it by either:

1. Following the steps noted in which repair the underlying cause (a broken registry key). The instructions relate to an earlier issue which broke the same registry key.


2. Repairing your Visual Studio installation via Add/Remove programs (this will take longer)

As mentioned, we would also like to understand whether customers experiencing the issue have recently installed any new pieces of software on the affected machines which stopped the find feature working as described in the bug. Please let us know via the Comments on this Connect item.

Mark Wilson-Thomas
Visual Studio Editor Team
Posted by Mark [MSFT] on 5/2/2014 at 9:28 AM
Warren, thanks for letting us know.

At present we are not sure of the root cause behind this registry key being overwritten/set empty. We have had similar issues in the distant past which were related to installation of the MSDN library for VS2008 SP1 after a later version of Visual Studio was installed.

Was this always a problem on your installation or did it start occuring at some point? Had you recently installed any new pieces of software on your machine (e.g. MSDN Library?) when the problem occurred?

Mark Wilson-Thomas
Visual Studio Editor Team
Posted by Warren Milward on 5/1/2014 at 10:25 PM
The problem for me was that the registry key HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32 was empty. Setting the default value to "C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\TextMgrP.dll" fixed the issue. The stack overflow answer provided by mikeidge has more details.
Posted by Mark [MSFT] on 4/29/2014 at 1:10 PM
Thanks for letting us know about the reg key workaround you've found Mike.

We will take a look at this information to see if we can discover a root cause for this reg key being changed.

Mark Wilson-Thomas
Visual Studio Editor Team
Posted by mikeidge on 4/9/2014 at 6:14 AM
I've found a fix. See the attached .reg file in Answer found here:
Posted by mikeidge on 4/8/2014 at 4:16 AM
Ah, the attachments are there now. My browser kept timing out because the site is so slow, so I didn't think they'd made it.
Posted by mikeidge on 4/8/2014 at 4:08 AM
I'm trying to add attachments to this entry as requested to no avail, so you'll have to e-mail me directly if you need those.

I can confirm that this is *not* project-specific. It never works in any project in which I try to search. Also, I've tried exporting and resetting my settings file which didn't help. Neither did the /resetuserdata switch.
Posted by Mark [MSFT] on 4/2/2014 at 6:12 PM
Hi @mikeidge

Thanks for raising this issue.

We have so far been unable to reproduce the behavior you describe. It would be useful if you could provide:

1. A set of screenshots or video of the issue in action
2. A project that shows the issue for you (assuming this does not repro for brand new projects created via fIle new project on your machine)?

VIsual Studio Editor Team
Posted by Microsoft on 3/25/2014 at 9:09 PM
Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information. If you require immediate assistance with this issue, please contact product support at
Posted by Microsoft on 3/23/2014 at 9:21 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you to submit the additional information we requested. If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.
Posted by Microsoft on 3/18/2014 at 7:45 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Please export and reset environment settings file by clicking Tools-> Import and Export Settings. If this issue does not persist after that, please zip the settings file and send it to us so that we can conduct further.

Please try this (from a Visual Studio command prompt with devenv in the path):

devenv /resetuserdata

Please submit this information to us within 4 business days. We look forward to hearing from you with this information. If you require immediate assistance with this issue, please contact product support at
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 3/18/2014 at 4:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at