Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: shansen on October 10, 2018, 04:47:34 am
-
Shane,
Using Windows Home (v1803 64-bit), post running Windows Repair (v4.3.0) All Repairs,
Windows Defender has been disabled. I am unable to re-enable it. I am hoping to avoid a clean install.
I have attempted to resolve the issue with the approaches listed in:
- https://www.tweaking.com/forums/index.php/topic,2732.msg18391.html#msg18391
- https://www.tweaking.com/forums/index.php/topic,3563.msg25528.html#msg25528
- https://www.tweaking.com/forums/index.php/topic,4790.0.html
And associated links:
- https://winaero.com/blog/disable-defender-windows-10-fall-creators-update/
- https://www.groovypost.com/howto/take-full-permissions-control-edit-protected-registry-keys/
All to no avail. Please refer the attached pictures are you able to assist?
Thanks
Shannon
-
As there have been other problems reported about WD and the repair program, I'll pass this onto Shane.
I'm not sure if you have used the registry restore option in the repair program to see if that resolves.
If you are using Win 10 Home so don't have gpedit then you can enable it by opening a Command Prompt (Admin) or Powershell (Admin) and entering this cmd - you can copy & paste it to the cmd prompt, but create a restore point first.
dism /online /norestart /add-package:"%SystemRoot%\servicing\Packages\{{Microsoft-Windows-GroupPolicy-ClientExtensions-Package".mum}}
To access GPE press the Windows key+r then type gpedit.msc and press enter.
Should you need to take ownership of a file, use the batch file in this article to add Take Ownership to the right click context menu.
https://www.tenforums.com/tutorials/3841-add-take-ownership-context-menu-windows-10-a.html
-
Please find below the returned message from Command Prompt (Admin) (Windows Home v1803)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Image Version: 10.0.17134.345
An error occurred trying to open - C:\WINDOWS\servicing\Packages\{{Microsoft-Windows-GroupPolicy-ClientExtensions-Package.mum}} Error: 0x80070003
An error occurred trying to open - C:\WINDOWS\servicing\Packages\{{Microsoft-Windows-GroupPolicy-ClientExtensions-Package.mum}} Error: 0x80070003
Error: 3
An error occurred trying to open - C:\WINDOWS\servicing\Packages\{{Microsoft-Windows-GroupPolicy-ClientExtensions-Package.mum}} Error: 0x80070003
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
-
Well I got that cmd from a Windows help article, but try the batch file in this article which includes instructions for its installation.
I used a batch file from another article for mine but was unable to get the page to open, so posted that cmd instead.
http://m.majorgeeks.com/files/details/group_policy_editor_for_windows_10_home_edition.html
-
While you aren't getting the message that this article refers to but if you have managed to include the GPE in your version of Win 10, see if the steps in this article will help.
https://www.quora.com/The-app-is-turned-off-by-group-policy-This-is-the-message-I-am-getting-when-I-am-trying-to-access-Windows-Defender-What-can-I-do
-
As I understand it, I am unable to access Group Policy Editor (gpedit.msc) in Windows Home.
Attempting to restart "Virus & threat protection" results in the error "unexpected error..." (attached).
-
I have capitulated. I have restored the registry from the initial Windows Repair Registry Backup.
Windows Defender runs as expected. :)
I initially ran Windows Repair in the hope of resolving a repeating sporadic BSOD issue.
With reverting to Backup, I am now unaware what, if any, repairs remain.
-
BSODs are usually caused by driver issues or conflicting programs so the repair program will not have helped with those.
I'll ask one of the members to take you through the procedure for BSOD diagnostics to see what was the cause of those.
-
I'd forgotten that Win 10 has its own BSOD troubleshooter which you can try to see what it reports.
Click on the Windows key/ Settings cog/Update & Security/Troubleshoot where you'll see the one for BSOD to click on.
-
Comically, Settings will not open. I am working through the fixes listed on https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-settings-not-working/a3e7d34c-1358-456e-a66b-7ad8906e0a30
-
It's quite possible that the powershell cmd should resolve but try a cold boot first.
This is done by shutting down, remove all power sources and hold the power button in for ~30secs and then see how things are after the boot up.