Some settings are managed by your organisation.

fdegrove said:

Hi,
That's quite likely due to a file version conflict.
Replacing gpedit.msc with a version corresponding to the W10 version of that machine should resolve this.


Cheers,

W10 Pro on my desktop has a copy of gpedit.msc and gpedit.dll in C:\Windows\System32 and copies in various WinSxS folders. Do I just copy over the gpedit.msc and gpedit.dll files in C:\Windows\System32 to my laptop runnig W10 Home or is it more complicated than that?

Hi,
Just copy the files to every folder you find them on the Home machine.
If after that sfc /scannow is still complaining then you may have to copy them to the WinXs folders as well but I doubt it.

Cheers,

cottonball said:

Could this help:

How To Enable Group Policy Editor (gpedit.msc) In Windows 10 Home Edition

I tried that but then sfc /scannow doesn't run without errors which I don't like.

You could try it with a script (no need to download .exe). Save this as a .bat file, run as administrator then reboot...

Code:

@echo off 
pushd "%~dp0" 
dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt 
dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt 

for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"C:\Windows\servicing\Packages\%%i" 
pause

source