Jump to content

HKLM\Software\wow6432node\updater


Recommended Posts

  • Replies 58
  • Created
  • Last Reply

Top Posters In This Topic

mmm, those settings are all correct. Try opening the hidden admin account see how that account responds...

Open an elevated Command Prompt

At the prompt type or copy paste net user administrator /active:yes select enter.

Close out and reboot, you will see a new account "Administartor" select it and follow the prompts through.

can you access or use Windows Defender..

Link to post
Share on other sites

Hiya joghurtbubi,

Try the following:

Download attached fixlist.txt file (end of reply) and save it to the Desktop, or the folder you saved FRST into. "Do not open that file when running FRST fix"
NOTE. It's important that both FRST and fixlist.txt are in the same location or the fix will not work.

Open FRST and press the Fix button just once and wait.
The tool will make a log on the Desktop (Fixlog.txt) or the folder it was ran from. Please post it to your reply.
 
That fix should force a reboot, if not reboot yourself. Part of the fix will also rehide the Admin account...
 
Thank you,
 
Kevin...

 

fixlist.txt

Link to post
Share on other sites

Hiya joghurtbubi,

I assume you are still unable to access Windows Defender..? continue:

Open elevated command prompt, type or copy paste:

net user administrator /active:no select enter

Reboot, that will rehide Admin account.

Next,

Download attached fixlist.txt file (end of reply) and save it to the Desktop, or the folder you saved FRST into. "Do not open that file when running FRST fix"
NOTE. It's important that both FRST and fixlist.txt are in the same location or the fix will not work.

Open FRST and press the Fix button just once and wait.
The tool will make a log on the Desktop (Fixlog.txt) or the folder it was ran from. Please post it to your reply.
 
That fix should force a reboot, if not reboot yourself.
 
Does Windows Defender now work, if not I`ve attached WinDefend.zip Unzip that file to your Desktop so you have WinDefend.reg
 
Double click on WinDefend.reg agree any merge alerts. Reboot when complete. Any change..?
 
Thanks,
 
Kevin

fixlist.txt WinDefend.zip

Link to post
Share on other sites

Download Farbar Service Scanner from here: http://www.bleepingcomputer.com/download/farbar-service-scanner/dl/62/ and run it on the computer with the issue.

Make sure the following options are checked:
 
  • Internet Services
  • Windows Firewall
  • System Restore
  • Security Center/Action Center
  • Windows Update
  • Windows Defender
 
  • Press "Scan".
  • It will create a log (FSS.txt) in the same directory the tool is run.
  • Please copy and paste the log to your reply.
Link to post
Share on other sites

Hello again joghurtbubi,

Thanks for the update, ok continue with the following:

Create a new restore point: https://support.microsoft.com/en-gb/help/4027538/windows-create-a-system-restore-point

Next,

Download Portable Windows Repair (all in one) from one of the following:

http://www.majorgeeks.com/mg/getmirror/tweaking_com_windows_repair_portable,1.html

https://www.bleepingcomputer.com/download/windows-repair-all-in-one/

Unzip the contents into a newly created folder on your desktop.

Open the folder, double click on Repair_Windows.exe to run the tool, agree any alerts.

Agree EULA as the tool opens...

From the upper menu bar select "Repair Mains" tab.

From the new window select "Preset: All Repairs"

From the new window select "Reboot to Safe Mode"

When your systems is back in Safe Mode select "Start Repairs"

When complete reboot your system to normal mode.

Is there any improvement..

Logs are saved to the Tweaking.com folder on your Desktop, the one to post is _Windows_Repair_Log.txt
 
Thank you,
 
Kevin...
Edited by kevinf80
typing error
Link to post
Share on other sites

Can you zip up and attach C:\Windows\minidump folder, you will have to copy to the desktop first. If it contains munidump files we may be able to see what caused the crashes...

Tweaking tool did reset many of the services that may have been causing or contibuting to the initial issues you had, I was quite surprised when the issues still remained. I believe we are now at the point when a system refresh or even possibly a reset is the only way forward....

The following link gives information for both refresh or reset:

https://www.tenforums.com/tutorials/4090-refresh-windows-10-a.html

Link to post
Share on other sites

Hello joghurtbubi,

There were three files in the dump folder as follows:

hal.dll      24/4/2020 - when it happened

hal.dll      23/5/2020 - when it happened

fltmgr.sys 10/6/2020 - when it happened (latest one)


Read the following for hal.dll - https://www.processlibrary.com/en/directory/files/hal/19411/

Regarding fltmgr.sys This is a more critical driver and can leave you unable to login to your system when you boot, if you experience more BSOD attributed to that driver each time it can end up as I describe initially.

The following link gives lots of information about this driver with possible fixes https://www.thewindowsclub.com/fltmgr-sys-blue-screen-windows/

If you do not intend refreshing your system please follow the instructions in that link to run SFC and CHKDSK. There is also a contained link to show how to run BSOD troubleshooter if necessary...

Before going for a refresh or reset run SFC and CHKDSK and see what information is returned...
 
Thanks,
 
Kevin...
Link to post
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.