Windows 10 Insider Preview Slow Build 18362.10012 & 18362.10013 (19H2) Insider

Page 4 of 4 FirstFirst ... 234

  1. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #30

    Kari said:
    Just a theory, as I have never been interested nor used Slow Ring and Release Ring builds, I have no idea if this works or not.

    As far as I have understood, Release Preview allows user to stop receiving Insider builds, leave Insider program. Wouldn't this make the updated Release Preview build to "official" general availability 1903? If so, wouldn't it then be possible for the user to re-join Insider program, this time selecting Slow Ring?

    Kari
    Possibly that would work, but It appears the OP has gone beyond that point, and is no longer seen as Release Preview by MS. Looks like it's trying to install 10005, which may be a pre-req to 10012 or 13. Most likely best to follow the recommended procedure of a base 18362, and go from there.

    EDIT: Been a while since I first set that up, but now I recall what I did. I had an RP in a VM that I simply switched to Slow because it was on the correct 18362, and it just went ahead and updated to 18362.10000, I believe it was. For a physical, I created a new partition and clean installed the latest ISO from MCT, and switched it to Slow after it was all updated.
    Last edited by f14tomcat; 11 Aug 2019 at 07:23.
      My Computers


  2. Posts : 13
    Windows 10
       #31

    Just got *12... borked my search, can't get it back.

    MS have failed at search since 1995, how hard can it really be?

    Windows 10 Insider Preview Slow Build 18362.10012 & 18362.10013 (19H2)-brokensearch.jpg

    AUTOMERGED - SOMETIME LATER...

    A day or so later...

    I was led to believe that MS were disconnecting Cortana from local search? It seems they're going the other way.

    The following key used to have no effect on local search, it now blocks local search entirely if set to '0' (zero).

    Code:
    HKCU\Software\Microsoft\Windows\CurrentVersion\Search\CortanaConsent
    .
    So now it seems that you can't universally disable Cortana without killing local search... which seems to me to be the opposite of separating the two "features". No?
      My Computer


  3. Posts : 30,530
    Windows 10 (Pro and Insider Pro)
       #32

    djmcnz said:
    Just got *12... borked my search, can't get it back.

    MS have failed at search since 1995, how hard can it really be?

    Windows 10 Insider Preview Slow Build 18362.10012 & 18362.10013 (19H2)-brokensearch.jpg

    AUTOMERGED - SOMETIME LATER...

    A day or so later...

    I was led to believe that MS were disconnecting Cortana from local search? It seems they're going the other way.

    The following key used to have no effect on local search, it now blocks local search entirely if set to '0' (zero).

    Code:
    HKCU\Software\Microsoft\Windows\CurrentVersion\Search\CortanaConsent
    .
    So now it seems that you can't universally disable Cortana without killing local search... which seems to me to be the opposite of separating the two "features". No?
    Something else is blocking your search... Search is working fine here, and CortanaConsent is set to 0
      My Computers


  4. Posts : 13
    Windows 10
       #33

    AndreTen said:
    Something else is blocking your search... Search is working fine here, and CortanaConsent is set to 0
    In that case it must be a combination of multiple flags, the others I do not know. If I toggle the consent flag and restart SearchUI.exe I can break and fix search at will so that flag is certainly being considered in the execution chain.

    Regardless, the message from MS is that they're separating the functions, 'CortanaConsent' should have no effect on local search and, as of the *12 update it does, and it didn't before. At the very least they should be telling us when they modify the behaviour of any group policy setting...
      My Computer


  5. Posts : 68,668
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #34
    Last edited by Brink; 27 Aug 2019 at 17:20.
      My Computers


  6. Posts : 1
    Windows 10
       #35

    djmcnz said:
    In that case it must be a combination of multiple flags, the others I do not know. If I toggle the consent flag and restart SearchUI.exe I can break and fix search at will so that flag is certainly being considered in the execution chain.

    Regardless, the message from MS is that they're separating the functions, 'CortanaConsent' should have no effect on local search and, as of the *12 update it does, and it didn't before. At the very least they should be telling us when they modify the behaviour of any group policy setting...
    Same issue here, edit the CortanaConsent value to 0 solve the problem... Thanks for this tip!
      My Computer


 

  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 06:31.
Find Us




Windows 10 Forums