Windows – Using make from Windows PowerShell

You could exclude zip files from the index but I know that isn't really answering your question. I use a freeware program called Everything that lets me choose what files to index and you can use regular expressions in that search in order to get more exact results (like what you're looking for). As far as I'm aware, windows search doesn't allow regular expressions but maybe you can attach a second parameter to the search like *zip*.* && not *.zip Not sure if that's possible though.

Edit: Since I (Karan) just tweaked Codezilla's last attempt posted in chat, it wouldn't be proper to add it as a separate answer. All credit goes to him (Edit: and to Scott as well) for discovering 95% of this search term, which seems to correctly identify the 10 valid filenames and leave out the 6 invalid ones:

*zip* NOT "*.*zip*" OR filename:"*zip*.*zip*"

So it can be done, but not without jumping through hoops. Confirmation of the fact that Windows Search sucks. Couldn't they have simply added proper RegEx support?

Solved!

Don't forget to rename the PowerShell folder in the 64-bit folder! I think that did the trick.

1. Win+R
2. C:\Windows\System32
3. Enter
4. Rename "WindowsPowerShell" to "WindowsPowerShellOld".
5. Win+R
6. C:\Windows\SysWOW64
7. Enter
8. Rename "WindowsPowerShell" to "WindowsPowerShellOld".

If you get any UAC prompts just click to confirm or provide a password if needed, and click on Continue if you get any warning about performing these operations.

You should definitely try uninstalling KB968930 first (as noted above) and see if that works. If you encounter any errors uninstalling this like I did or if the Windows setup program still says you need to uninstall PowerShell to continue even after you have removed KB968930 then try renaming these folders.

I would suggest that you skip the registry trick at first, and that you skip taking ownership of these folders. Just go straight to the folders in Windows Explorer and try renaming them as noted above. If you are unable to rename them, go ahead and make the registry change (as noted above) and also take ownership of these folders.

Alternatively, you can rename the folders as "WindowsPowerShell2". I don't know if this has any effect on it. It really should not. This is actually the bogus name I used last time. But I think the really important thing is to rename the folder inside C:\Windows\SysWOW64.