Lenovo Thinkserver Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu

When trying to install Windows Server 2012 R2 Standard, I cancelled (red X after installation started) the first installation because I accidentally chose the wrong partition when starting the installation, so this brought me back to the install menu, I tried to delete all the partitions and start repartitioning (I wanted a 50gb, 50gb, and remainder (467GB or something, from the 600GB Raid I had).  It would not let me delete the 467GB partition, and showed it was using a little bit of space.  It said the partition was in use, so I assumed that since I hadn't rebooted since cancelling the installation, that the first install had left it in use.  So I proceeded to go back to the first install menu and chose Repair instead (no reboot in between yet).  Using diskpart I tried to delete the partition once again, and I couldn't.  There was a folder and a winPE swap file on the partition.  At this point I figured I had to reboot to get any further.

I rebooted, proceeded through the install steps to the partitioning screen again, was then able to delete the partition, but when trying to create a new partition, it created it, but didn't put any of the regular special partitions in front of it... I knew something was wrong at this point, and after creating a new 50GB partition, there was a message at the bottom of the install window stating "Windows can't be installed on this drive. (Show Details)" and clicking details showed the next error window:

Windows Setup
Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu.

At this point I'm starting to get frustrated.  I go into the windows repair options, run a command prompt, run diskpart, delete all the partitions (if any), try a "select disk 0" or whichever disk you are trying to use ("list disk"), "clean disk".  I'm thinking this is going to cure everything.

I reboot back into the windows install but get the same message at the partitioning screen.

I'm stumped, googling doesn't find too much, other then one entry for SAN's and similar systems where a flag may have to be set manually to allow windows to install to the disk (over-riding a security/safety feature), I try using diskpart to see if I can set this option but can't find a way, and try setting Boot Disk to yes using diskpart, but can't seem to do that or find how to do that either.

I revert back to trying to re-initialize the RAID-10 I've created on the 720ix raid controller that's built into the Lenovo Thinkserver TD350 server, this doesn't seem to help.  I try resetting the Virtual disk (erasing it), etc etc

Finally 2 hours into this endeavour I go back into the TDM (Thinkserver Deployment M....), and stumble upon the deployment tab/menu option that allows me to pick all my Windows options (partition, windows key, admin password, etc) and proceeds to do an automated install of Windows onto the Raid (one minor issue, it wouldn't let me create a partition smaller than 67GB for installing on, and I had only chosen one role (Hyper-V)... I was planning to do it with 50GB, oh well.

Before stumbling on the automated deployment tool in the bios, I was prepared to attempt clearing the Raid using Linux (in case windows MBR or something was still on the drive)... I don't really think this would have helped, but I was grasping at straws at this point, and wondering what had changed from the initial successful attempt to install windows (which I so wrongly chose to cancel apparently), and now... at this point I had reset bios settings, tried to see if there was a specific option to set the raid controller to a bootable device (thinking this was causing the error message during the partitioning and install phase)...

All I know is that at this point, the automated deployment I did from the Bios seemed to get things back in order again... I can't explain why it was failing to allow me create new partitions and continue the installation.

Windows 10 upgrade local Search not working, Cortana search not working, local search index failing

After a fresh upgrade from Windows 7 Pro to Windows 10 Pro on a laptop, I had a OneDrive.exe crash message that I wanted to save to research later, so I went to load up Snipping Tool to grab a copy of it, but I couldn't find Snipping tool using the Search bar beside the start menu.  The search menu would provide some web results, but nothing local that I could see.  I took a brief look through the Start Menu All Apps list and couldn't find Snipping Tool either, so I figured it may be missing from Windows 10 for some reason so I headed for some google searching to figure it out.

After researching Snipping Tool on Windows 10, everything pointed toward it being included by default, and it should just "be there"... eventually I stumbled across something that said to look under All Apps > Windows Accessories > Snipping Tool ... and there it was.. awesome, one issue solved and I get my screen shots of the OneDrive error.

This brings us to the issue at hand... why didn't the Search bar find Snipping Tool in the menu?  After a bunch of research, I tried a few things, tried the troubleshooters (built-in, etc), nothing worked until I did this:

1. Traverse to C:\ProgramData\Microsoft\
2. Rename the "Search" folder to "Search.old" or something similar
3. A new Search folder should appear almost immediately if the Windows Search Index is trying to generate a new index (you may need to trigger this otherwise)
4. eventually after the search index was recreated, my Search bar beside the Windows 10 Start menu now works and successfully found my beloved Snipping Tool, among other things obviously.

Notes:
There was something in the windows event viewer logs mentioning
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log

SearchIndexer (5628) Windows: Error -1811 (0xfffff8ed) occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log.

This is what led me to the folder we renamed, I saw files being created and deleted in real time while the index was trying to rebuild, but it could not rebuild and had other related error messages in the event log (none super helpful).

Caveats: I don't know if this will have any repercussions, but it recreated the folder in question, so I assume it will be okay.