Search boxes inside windows not working

Page 4 of 5 FirstFirst ... 2345 LastLast

  1. Posts : 919
    Windows 10 Pro 64bit 22H2 19045.3324
       #31

    IRIXUIH said:
    Today KB 4532695 released. But I still have File Explorer crash, just when I did a search in the search box in Taskbar.

    Farvatten said:
    Something I've also seen associated with this File Explorer search issue when it does appear, is there's often a corresponding Runtime Broker crash that shows up in my Reliability History.
    Under 1909 18363.592 I was immediately getting these Runtime Broker crashes under the Reliability Monitor with almost every search regardless of whether the search window froze or not, the Broker error details always pointing to Cortana which I don't use, having 'turning off' what I can about it.

    So far with 1909 18363.628 I haven't been able to get it to crash, nor has my search window gone dead, but I'll give it time and report back if I see it return.

    - - - Updated - - -

    While I've not had the File Explorer search window freeze on me under .628, I can still generate these Runtime Broker errors on demand by typing the 'search-ms:' protocol prefix into the File Explorer path window, a method previously mentioned to force the search window open.
    Attached Thumbnails Attached Thumbnails Search boxes inside windows not working-seach-ms_protocal.jpg   Search boxes inside windows not working-runtimebrokererrordetails.jpg  
      My Computers


  2. Posts : 19
    Windows 10 Pro 64bit 1909 with all latest updates
       #32

    @Farvatten
    I am on the same build of 1909. Yes, it still happens.
    I just search Windows for Reliability Monitor, to bring up the settings, and noticed while doing that, and while randomly in the background, the crash happens.
    Meanwhile, I mostly use Win key+I to go to settings, and within the settings, to search for Reliability Monitor. But that even didn't avoid the crash.
    Search boxes inside windows not working-2020-01-29_8-51-25.png
    Search boxes inside windows not working-2020-01-29_8-48-02.png
      My Computer


  3. Posts : 19
    Windows 10 Pro 64bit 1909 with all latest updates
       #33

    Rafael Rivera, posted about these issues as well, he also posted about a tool to disable the new Windows Search experience

    https://twitter.com/WithinRafael/sta...021498368?s=20

    - - - Updated - - -

    This is just for today after the update: kb4532695
    Search boxes inside windows not working-2020-01-29_20-26-31.png

    Thank you, Microsoft!
      My Computer


  4. Posts : 19
    Windows 10 Pro 64bit 1909 with all latest updates
       #34

    Win10 version 1909 File Explorer search box still buggy — but less so @ AskWoody

    "File Explorer’s unified search experience is still a mess and it looks like things won’t get better until Windows 10’s 20H1 update is out. Microsoft has yet to acknowledge the new problems with Explorer and there don’t appear to be any workarounds. If you have installed Windows 10 November 2019 Update, you have to accept the possibility of experiencing issues with File Explorer and Control Panel."
      My Computer


  5. Posts : 13
    Win 10 Pro (x64) 21H1 (build 19043.1165)
       #35

    Re: January 28, 2020 - KB4532695
    https://support.microsoft.com/en-ca/...date-kb4532695
    "Updates an issue that prevents File Explorer's Search Bar from
    pasting clipboard content using the right mouse button (right-click)
    and prevents File Explorer's Search Bar from receiving user input".

    As I am unable to install KB4532695 (due to error 0x80070002) as a
    temporary fix, I wrote a small BAT file that will blow explorer's nose
    and make it work again... (for a while).

    TaskKill /f /im explorer.exe
    Timeout 2
    Start explorer.exe
    Exit

    Peter "Backspace"
      My Computer


  6. Posts : 19
    Windows 10 Pro 64bit 1909 with all latest updates
       #36

    @Backspace Do not install it. Here is why:
    Patch Lady – don’t install optional updates Patch Lady – don’t install optional updates @ AskWoody
      My Computer


  7. Posts : 13
    Win 10 Pro (x64) 21H1 (build 19043.1165)
       #37

    Thank you, IRIXUIH,

    I think I'll take your advice and postpone optional updates until the "Semi-Annual" is released.
    I can pass on any BSOD's.

    Peter (Backspace)
    in Trumpless Canada
      My Computer


  8. Posts : 17,013
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #38

    See KB4535996 CU Win 10 v1903 build 18362.693 and v1909 build 18363.693
    and its MS original https://support.microsoft.com/en-us/help/4535996

    You have to read both the v1909 & v1903 bits to see all the identified issues that the update addresses. They include
    - Addresses an issue that prevents the Windows Search box from rendering fully in the space allotted for it.
    - Addresses an issue that might prevent the Windows Search box from showing results.

    Denis
    Last edited by Try3; 27 Feb 2020 at 19:58.
      My Computer


  9. Posts : 19
    Windows 10 Pro 64bit 1909 with all latest updates
       #39
      My Computer


  10. Posts : 919
    Windows 10 Pro 64bit 22H2 19045.3324
       #40

    Farvatten said:
    Under 1909 18363.592 I was immediately getting these Runtime Broker crashes under the Reliability Monitor with almost every search regardless of whether the search window froze or not, the Broker error details always pointing to Cortana which I don't use, having 'turning off' what I can about it.

    So far with 1909 18363.628 I haven't been able to get it to crash, nor has my search window gone dead, but I'll give it time and report back if I see it return.

    - - - Updated - - -

    While I've not had the File Explorer search window freeze on me under .628, I can still generate these Runtime Broker errors on demand by typing the 'search-ms:' protocol prefix into the File Explorer path window, a method previously mentioned to force the search window open.
    Update: Currently still no File Explorer search window freezes since 18363.628 or now after 18363.693.

    Apparently some other promising news, the chronic Runtime Broker errors I'd been getting immediately after almost every search in the Reliability Monitor and or by using the 'search-ms:' protocal prefix, and was still getting after 18363.628 have NOT shown up since Thursday the 27th's 'D' release of 18363.693.
    Last edited by Farvatten; 03 Mar 2020 at 13:54.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:31.
Find Us




Windows 10 Forums