Build 10547 - I haven't changed anything I know of, but this is my insider settings:
Where did "Disabled" come from? Well, I know where, but I suppose I want to know why it's changed and want it back to fast ring.
Here's the relevant Registry entry - what should it be changed back to?
Are you logged in with your Microsoft account or a local account?
Microsoft Account - I changed the real account name to account.hotmail.com in the first screenshot - it says I am ready to receive insider builds.
Here's a backup of the registry key from 21st August, which I think it was set to when I was running 10532 before upgrading to 10547
I'm going to merge that key back into the registry, reboot and see what happens...Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="WIF" "ThresholdRiskLevel"="low" "EnablePreviewBuilds"=dword:00000002 "RingBackup"="WIS" "AdminFlowsValidateFlightSettingsHr"=dword:00000000 "FlightingOwnerGUID"="9185273e-b273-4b26-916c-56ae88ed64de" "BranchName"="th2_release" "UserPreferredBranchName"="th2_release" "ThresholdOptedin"=dword:00000001
... Which seems to have returned me to the fast ring. Curious.
Last edited by Fafhrd; 29 Sep 2015 at 10:13.
Dang! My fingers have all gotten tangled up, and my cheeks are hot...
Well, it's happened again. Disabled instead of Fast ring. I had checked for updates at about 11.15, which is shown in the ring timestamps. Still activated.
There are also a couple of new subkeys under WindowsSelfHost that have appeared:
Can anyone say what's going on? Should I leave it this way or revert the registry entry as I did before?Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="Disabled" "ThresholdRiskLevel"="low" "EnablePreviewBuilds"=dword:00000002 "RingBackup"="WIF" "AdminFlowsValidateFlightSettingsHr"=dword:00000000 "FlightingOwnerGUID"="9185273e-b273-4b26-916c-56ae88ed64de" "ThresholdOptedin"=dword:00000001 "BranchName"="th2_release" "UserPreferredBranchName"="th2_release" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\PreMigration] "FlightedBuildBranchName"="th2_release" "FlightedBuildRingName"="WIF" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Timestamps] "BranchNameTimestamp"="2015-09-19 12:40:38.121" "bBranchNameTimestamp"=hex:7d,e3,fa,62,d8,f2,d0,01 "RingTimestamp"="2015-10-09 23:15:07.919" "bRingTimestamp"=hex:bb,19,9c,56,e8,02,d1,01
What do other insiders see when they look at this registry entry?
Last edited by Fafhrd; 10 Oct 2015 at 02:27.
Well, I reverted the registry key to what it was previously (as in #3) and deleted the Timestamps and PreMigration Subkeys a couple of days ago, and I was back on Fast Ring, and am installing 10565 now.
The installation was uneventful until the screen immediately preceding the lock screen: -
Then logon was normal.
The PreMigration subkey has reappeared, but not the timestamps subkey.
I am still wondering what others see under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost
- especially those that have irregularities with their insider behaviour, as well as those with totally normal insider systems.
Last edited by Fafhrd; 12 Oct 2015 at 18:57.
Trying to install during a ballgame just missed another Cubs home run wow! Better go back to game.
Quote
