New
#1
v1607 Insider Preview build settings need attention
After the Anniversary update I have "Your insider preview build settings need attention. Go to Windows Insider Program to fix this issue.". Any idea?
![]()
After the Anniversary update I have "Your insider preview build settings need attention. Go to Windows Insider Program to fix this issue.". Any idea?
![]()
One option is to login with Microsoft account, start using Insider builds, then stop it again, delete Microsoft acccount and use local account again. The problem is that it appears again if you go to the Windows Insider Program settings menu.
I'm waiting for advice too, if we can fix it or just wait for Microsoft.
What ideas are you looking for? What don't you understand?
Well, I'm personally not using and have never used any Insider build on desktop PC, so this recommendation what there is showing "Go to Windows Insider Program to fix this issue" is not helping at all. There is no Insider Program, so there is no option to fix anything. Still this "warning" is there.
It started showing after update from v1511 to v1607 on regular non-insider machine.
edit:
so, there is one brute-force option to "remove" this message
navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\UI\Strings
(make sure you have a backup) and delete here every entry (except first one).
however as I said, it will be back as soon as you navigate to Windows Insider Program menu in Settings, so do not touch that :)
I hope there will be some proper fix.
All in all it is basically just a cosmetic thing. (I belive though)
Last edited by eddward; 04 Aug 2016 at 14:56.
You can actually just go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\UI\Visibility and change DiagnosticErrorText and DiagnosticLink to 0 instead of 1 and you get the same result .. and if you go back to the Insiders page it will return like you say...
This could be an issue with your PC .. I have noticed weird warnings like this before ... saying that Admin Policies have made changes or something like that even though I never modified any policies... turns out that its Spybot Anti-Beacon which is used to stop a lot of Microsoft's spying crap in Windows 10 ... So if you use that ... this error may be because of that and probably can be ignored.