Skip to content

Hyper-V causes Windows Indexing fail

Recently we mentioned a report about consistent failures of Windows Indexing that was finally solved by disabling Hyper-V.

We’re now confident that there’s a conflict, because we’ve had two more reports from readers of the same problem and solution.

Thanks for the coverage of Windows indexing problems. I spent a lot of time on this… rebuilding and moving indexes, trying options for repairing psts etc and they didn’t work.

As soon as I disabled HyperV the problem was solved – as per your report. I could not even find this solution anywhere, including Microsoft’s page for troubleshooting indexes.

I agree with you that it is third rate for Microsoft not to make this solution widely available or, better still, fix the problem so it doesn’t occur. I am a Microsoft fan overall but some things are just inexplicable. ”    Jim B.

Another fixed the problem through sheer trial and error.

Why keep it a secret?

Microsoft knows about this bug, their own tech support told one of our readers to disable Hyper-V.    We have a copy of the MS support email to confirm it.

But there’s no Knowledge Base article, let alone a fix for this bug.

Anyone who thinks that all bugs and problems are listed in the Microsoft Knowledge Base is deluding themselves.  The KB only lists bugs that Microsoft is prepared to admit or have been forced to admit.

This bug is embarrassing and therefore Redmond wants to keep it quiet.   It involves only Microsoft products, so they can’t blame a third party.  The bug has been there for a while, so it’s even more embarrassing.  And Microsoft hasn’t released a patch, which adds yet more shame.

Microsoft’s secrecy is good for the company, but awful for customers.  Each affected customer wastes many hours of their time on a problem that could be quickly fixed if Microsoft posted details of the bug and how to workaround it.  But, of course, Microsoft doesn’t have to pay for customers time so they don’t care.

Hyper-V and Indexing fail … sometimes

Microsoft should come clean about this bug, if only to reassure customers.  Plenty of customers use Hyper-V without indexing problems so Microsoft should disclose why others are having a problem.

We don’t know if the bug is limited to Windows 7 or also troubles Windows 8.

Happily, the people we know with this indexing bug don’t need Hyper-V (probably didn’t know it existed) so disabling it wasn’t a problem.    Other users might not be so lucky.

What to do

Microsoft’s conspicuous silence makes it hard to give reliable advice.  As a precaution, you should make sure Hyper-V is disabled, IF you don’t need it (or know what it is).

Many people don’t have to worry.  Hyper-V is only available on high end versions of Windows.  That’s Windows 8 Enterprise or Professional 64-bit or similar in Windows 7. In addition, some installations don’t include Hyper-V right away, you add it from Control Panel | Programs if needed.

To see if you have Hyper-V and its status go to Control Panel | Administrative Tools | Services.  Scroll down the list until you find a collection of Hyper-V services.

If there’s no Hyper-V entry – you’re good and there’s no action needed.

If you see Hyper-V listed and don’t need it, look at top left and click Stop for each.  That might be enough to fix the problem (only Microsoft knows for sure and they aren’t talking).

It might be necessary to disable Hyper-V.  To disable Hyper-V in Windows 7, open a command prompt with administrator privileges then run the command

 sc config "HyperW7Svc" start=disabled  

About this author

Office-Watch.com

Office Watch is the independent source of Microsoft Office news, tips and help since 1996. Don't miss our famous free newsletter.