Something in the background at work with Applicability in the registry. Immediately after upgrading to build 10135 my settings were: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="OSG" "ThresholdInternal"=dword:00000001 "ThresholdOptedin"=dword:00000001 "ThresholdRiskLevel"="low" "EnablePreviewBuilds"=dword:00000002 "RingBackup"="WIS" Thirty minutes after upgrading to build 10135 my settings were: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="WIS" "ThresholdRiskLevel"="low" "EnablePreviewBuilds"=dword:00000002 "RingBackup"="OSG" "BranchName"="fbl_impressive" "UserPreferredBranchName"="fbl_impressive" Now at two hours after updating to build 10135 my settings are: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="WIF" "ThresholdRiskLevel"="low" "EnablePreviewBuilds"=dword:00000002 "RingBackup"="WIS" "BranchName"="fbl_impressive" "UserPreferredBranchName"="fbl_impressive" "ThresholdOptedin"=dword:00000001 I do not know what to make of these changes or what is making these changes. Just thought it kinda of odd. In the past it required an update to make these kind of changes. Also if you have upgraded to either 10134 or 10135 you might want to check which Ring you are now on in Settings. In my case both upgrades changed my Ring to Slow.
what you think? it is a bird some 5 feet tall and tastes terrible if you make mistakes. Btw it feeds a 4 head family many weeks .... lol
Mine is as such after 3 hrs at least Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="Disabled" "EnablePreviewBuilds"=dword:00000002 "RingBackup"="OSG"
Just upgraded to 10135 and now the wifi connect icon shows Limited. The wifi adapter is DLink DWA-140. I've never had any problem with it after several Win10 installs on another PC until now.
I have experienced that right from build 10122 till build 10130. Indeed, I thought it has something to do with setting the PIN in previous build, but I might be wrong.