This was a fresh install... I enabled the search with mach 2 ...So clicking on 1 doesn't bring the tab up on 2?
Attachment 237088
Odd. Might be worth DISM restorehealth and a system file checker before you try a refresh or clean install. At least you have a backup. Sorry to be of no help
As much as I like Thurrott I don't use third party Windows frigs to try and get something to work, especially on a Skip version of Windows. Just my humble opinion although some do it as a hobby....
P.S. good luck in finding an answer to your problem.
And Microsoft doesn't recommend the use of those tools either, they can cause "unknown issues" in the OS:
New Windows 10 Insider Preview Fast Build 18348 (19H1) - March 1
New Windows 10 Insider Preview Fast & Skip Ahead Build 17704 - June 27
Without that tool..I get 0 new features lol...anyways I'm gonna dig around to see why I don't have search tools near view
EFI is on boot drive as directed by your Uefi-bios setup. Did you reinstall your operating system after changing your mobo?I have been unable to update Insider from build 18912 to 18917 using Windows Update. So I downloaded the files from UUPDump and mounted the ISO. But again the install failed at the last boot. The error messages don't given me enough info to know what has caused the failure, they're too vague or generic.
Perhaps my component changes have a bearing on this. I have just upgraded my desktop with new mobo, CPU, RAM and Video card (details in my system 1 specs.)
I dual boot W10 1903 (on a 250 GB NVMe card, in socket M2_1) and Insider (on a 500 GB NVMe card, in socket M2_2.) Both these cards, and my other drives are carry-overs from the previous installation.
Windows boot manager defaults to "Insider" on start up. But since installing the new components, often the boot fails with a message that "A required device isn't connected or can't be accessed" Error 0x000000e.
While there is normally no identification of what caused the failure, I have seen 'Winload.efi' listed as the offending file. Several copies of this file exist, including one in C:\Windows\System32\Boot
Using Esc to get out of that error screen, (which auto opens the BIOS page) then closing BIOS without making any changes results in a normal boot.
Do I need to repair the MBR?
The 250 GB NVMe card has an "EFI System" partition. The 500 GB NVMe card does not have an "EFI System" partition. This screen grab from Disk Management shows how the drives are partitioned. I have not attempted to alter how Windows set up the drives.
Attachment 237027
Attachment 237021Invalid attachment ????
Are these partitions correct? Does the fact that the larger (Insider) drive does not have an "EFI System" partition have any bearing?
Any and all suggestions on how to get "Insider" to update to build 18917 will be appreciated. I know a clean install may be the best solution, but I have many apps so a fix other than a clean install has its attractions
On a fresh install no mach 2...on another laptop the search tools is missing as well with the new search feature..
All I can say about the unified search feature started by MS is that it is a work in progress. The way I see it is that it is being tested and not set yet in stone. Meaning there is no way so far to fix it. I am having the same thing as Steven Campoli in a previous post in this build (no search bar at all, just a little box)
New Windows 10 20H1 test build brings Microsoft Search to File Explorer | ZDNetMicrosoft is switching up the search capability inside File Explorer so that it will now be powered by Microsoft's new unified search experience. It is starting to test this feature with a subset of 20H1 Insider Fast Ring testers.
JUst updated (WU) on a windows 10 vM running on a virtual esxi6.5 server. I think I may install this build on a harddrive as newegg just offered a 1TB ssd for under a hundred bucks, including a 3 yr warranty.
Quote
