Reply to thread

Message

<blockquote data-quote="jetman" data-source="post: 943026" data-attributes="member: 63028">Thanks very much for the replies !I have a &#039;clean&#039; Windows install saved as a Macrium image.&nbsp; I temporarily restored this image and tried out Edge.&nbsp; None of the settings were &#039;manged by my organisation&#039;.&nbsp; I then ran O&amp;O Shut Up 10 and applied all recommended actions.&nbsp; As you all confirmed this caused the &#039;manged by my organisation&#039; icon to appear next to various Edge settings.&nbsp; Good job I mentioned O&amp;O Shut Up 10 in my original post- it was just an afterthought.I then went back to current Windows 10 system to see if I could fix the problem with any of the solutions above.Creating a new Edge profile did not work.Installing O&amp;O Shut Up 10 and unchecking all of the system tweaks did not work. **see edit belowEditing the registry did not appear to work either.However- I then had an idea.I went back to my &#039;clean&#039; install of Windows and opened O&amp;O Shut Up 10 but did not make any changes.&nbsp; I exported the existing settings to an O&amp;O configuration file, which I saved on a USB.&nbsp; I then went back to my current system and changed it from a Standard User Account to and Administrator account.&nbsp;&nbsp; Next I downloaded O&amp;O, imported the configuration file from the &#039;clean&#039; system and applied the changes.&nbsp; After a re-boot, Edge was working normally again.I&#039;m still going to run O&amp;O Shut Up10 because it does a useful job.&nbsp; But I shall be careful about what settings I choose to alter in future.&nbsp; Its a shame we have a need for this software at all- I think its outrageous how these companies like to spy on their customers and its time governments stopped this from happening.Anyway- thanks for pointing me in the right direction.Very much appreciated !!** in retrospect that might have worked if I had firstly changed my SUA account into Admin account.&nbsp; (Running Shutup10 as an administrator within an SUA account does not have the same effect).&nbsp; PS- The suggested registry fix didn&#039;t work within an admin account however.</blockquote>

[QUOTE="jetman, post: 943026, member: 63028"] Thanks very much for the replies ! I have a 'clean' Windows install saved as a Macrium image. I temporarily restored this image and tried out Edge. None of the settings were 'manged by my organisation'. I then ran O&O Shut Up 10 and applied all recommended actions. As you all confirmed this caused the 'manged by my organisation' icon to appear next to various Edge settings. Good job I mentioned O&O Shut Up 10 in my original post- it was just an afterthought. I then went back to current Windows 10 system to see if I could fix the problem with any of the solutions above. Creating a new Edge profile did not work. Installing O&O Shut Up 10 and unchecking all of the system tweaks did not work. [SIZE=5][COLOR=rgb(184, 49, 47)]**[/COLOR][/SIZE][SIZE=3][COLOR=rgb(184, 49, 47)]see edit below[/COLOR][/SIZE] Editing the registry did not appear to work either. However- I then had an idea. I went back to my 'clean' install of Windows and opened O&O Shut Up 10 but did not make any changes. I exported the existing settings to an O&O configuration file, which I saved on a USB. I then went back to my current system and changed it from a Standard User Account to and Administrator account. Next I downloaded O&O, imported the configuration file from the 'clean' system and applied the changes. After a re-boot, Edge was working normally again. I'm still going to run O&O Shut Up10 because it does a useful job. But I shall be careful about what settings I choose to alter in future. Its a shame we have a need for this software at all- I think its outrageous how these companies like to spy on their customers and its time governments stopped this from happening. Anyway- thanks for pointing me in the right direction. Very much appreciated !! [COLOR=#b8312f]** in retrospect that might have worked if I had firstly changed my SUA account into Admin account. (Running Shutup10 as an administrator within an SUA account does not have the same effect). PS- The suggested registry fix didn't work within an admin account however.[/COLOR] [/QUOTE]

Verification