Delete GPEdit from Windows 10 Home

Page 2 of 2 FirstFirst 12

  1. Posts : 31,660
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #11

    seskanda said:
    What I do is simply backup the registry fully from the Regback folder....

    Have you looked inside the Regback folder recently? What version of Windows are you running? The last know version for which the RegIdleBackup task actually worked was 1709.


    the task now shows a Last Run Time of 7th Oct 2018 at 22:31 and a Last Run Result of (0x0). However the files in RegBack are still zero length and dated 19th July. Basically, it appears this task doesn't do the work it is supposed to do.
    Windows 10 crashed after update and is now unbootable Solved - Page 3 - Windows 10 Forums
      My Computers


  2. Posts : 9,790
    Mac OS Catalina
       #12

    Make the backup and try.
      My Computer


  3. Posts : 16,949
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #13

    If you really want a backup of the Registry despite the limitations on its use then you can use an alternative method that does still work - exporting each of the set of major Registry Keys instead.
    - The task can be automated using a batch file
    - The results are not as compact as the older method
    - The results do not establish a dependable basis for recovering from a problem
    - The results are nowhere near as useful as a system image

    Denis
      My Computer


  4. Posts : 29
    Windows 10 Home
    Thread Starter
       #14

    I was not aware that Regback backup of the registry does not save all the settings for Windows. But whenever I've done it in the past to recover from malware and similar issues it sure seemed to bring back Windows to close to 100% of how it was before for me. Anyways, this is not what the thread is really about so I like to focus on fixing the original problem first.

    Bree said:
    Have you looked inside the Regback folder recently? What version of Windows are you running? The last know version for which the RegIdleBackup task actually worked was 1709.
    Im using v1703 and it does what I need not happy to hear 1803 and above refuse to work with the Regback method. That's all I want to mention about this as it goes off topic from the thread.

    Its still not clear if /remove-package of the dism command will delete the directories and files inside the two folders mentioned in the .bat file. Let me know if you are able to find that out at all.

    bro67 said:
    Make a backup and try
    I just did this, but again its not what I'm going after here. It restricts access to gpedit.msc whereas before it was only disabled. I get a different error message window this time around when using this method. It used to say something like: 'Windows cannot find 'gpedit.msc' Now, it gives me: 'The Snap-in...in this document has been restricted by policy' followed by an MMC window that has another error.
      My Computer


  5. Posts : 42,985
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #15

    I was not aware that Regback backup of the registry does not save all the settings for Windows.
    System Restore is the function provided for people to restore things to a consistent state - registry and related files/programs/updates etc. However as is well documented here, using restore points is sadly not reliable.

    Example: Imagine you had just installed a program. Then you restored the registry from a copy created before installing the program. All files related to the program would still be present.

    My guess when we explored Regback its scheduled task was that that backup might have been related to the long gone Known Good Configuration. About the only use of such a backup is when registry corruption prevents the system booting and System Restore is also then not available, that in the absence of disk images.

    There are 3rd party registry backup programs with which you could schedule a registry backup, lacking Regback.
    Registry Backup
      My Computers


  6. Posts : 29
    Windows 10 Home
    Thread Starter
       #16

    System Restore was always a nightmare just by the amount of disk space it gobbled up. Nevermind the fact it rarely if ever actually worked. Anyway, after copying those two folders the .bat referenced, I went ahead and changed /add-package to /remove-package and after running everything is back to the way it was before

    Appreciate all for the help, especially Bree for the suggestion to edit the .bat file. Now, I can upgrade Home to Pro. One last question, if I use the way shown in website below will it keep my Windows 10 v1703 or update it to latest version?

    How to upgrade from Windows 10 Home to Pro for free | ZDNet
      My Computer


  7. Posts : 31,660
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #17

    seskanda said:
    One last question, if I use the way shown in website below will it keep my Windows 10 v1703 or update it to latest version?
    How to upgrade from Windows 10 Home to Pro for free | ZDNet
    There's a TenForums tutorial on that too...

    Upgrade Windows 10 Home to Windows 10 Pro | Tutorials

    ...basically upgrading Home to Pro by changing the product key is not actually a full OS upgrade, but just a way to unlock features already there in the installed OS but disabled in Home. I have done that upgrade on 1803, it takes just a few minutes, far too short to be a full OS replacement. You will still be using the same installed OS so will still be on 1703 in your case. There may be one or two components downloaded, but you won't get a Windows.old folder created as you are still running the same installed OS, just with the Pro features enabled in the registry.

    Note that upgrading from Home to Pro is a one way process, there is no official way to go back. So if you want the option to go back to Home, make a system image before you upgrade.
      My Computers


  8. Posts : 29
    Windows 10 Home
    Thread Starter
       #18

    Bree said:
    There's a TenForums tutorial on that too...

    Upgrade Windows 10 Home to Windows 10 Pro | Tutorials
    I somehow missed this it's very helpful as well. Bitlocker is worthwhile to have as is remote desktop, and of course Group Policy Editor.

    Bree said:
    ...basically upgrading Home to Pro by changing the product key is not actually a full OS upgrade, but just a way to unlock features already there in the installed OS but disabled in Home. I have done that upgrade on 1803, it takes just a few minutes, far too short to be a full OS replacement. You will still be using the same installed OS so will still be on 1703 in your case. There may be one or two components downloaded, but you won't get a Windows.old folder created as you are still running the same installed OS, just with the Pro features enabled in the registry.
    Can I use the product key from Windows 7 Pro on the bottom of my laptops to do this? That's reassuring it will stay on v1703 when going to Windows 10 Pro. I simply want to enable Bitlocker, Remote Desktop, and Group Policy Editor so no need for extensive changes here. I already have a Windows.old from the time a refresh was done no big deal then.


    Bree said:
    Note that upgrading from Home to Pro is a one way process, there is no official way to go back. So if you want the option to go back to Home, make a system image before you upgrade.
    Good to know this beforehand, will be sure to find a way to get back to how it was if I decide to upgrade in the long run.
      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 19:49.
Find Us




Windows 10 Forums