S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 9, 2019 #181 Okay, please close FRST, open my fixlist and remove the EmptyTemp:line and save. Then retry the fix.
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 10, 2019 #184 Still running. More than 30 hours...
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 14, 2019 #186 After 120 hours it's still running...
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 14, 2019 #187 Stop it. I'll modify the script.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 14, 2019 #189 Try this one: Attachments Fixlist.txt 3.2 KB · Views: 2
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 14, 2019 #190 If you don't get anything within one hour, please post back.
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 14, 2019 #191 Utility is running since 11:04 and not finished.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 14, 2019 #192 Please retry from Safe Mode. If no results within 1 or 2 hours, post back.
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 14, 2019 #193 I tried in Safe Mode as admin. After one hour of running without any visible result, I stopped it.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 14, 2019 #194 Let me know if this works. SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a log should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text. Attachments SFCFixScript.txt 87 bytes · Views: 1
Let me know if this works. SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a log should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 15, 2019 #195 Utility executed. Log attached. Attachments SFCFix.txt 1.9 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 15, 2019 #196 Let's do a small test. Please try the following fixlist.txt with FRST64 utility. Attachments Fixlist.txt 83 bytes · Views: 1
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 15, 2019 #197 After two hours of running nothing happens. Should I try to run it in Safe Mode?
E ekitep67 Well-known member Joined Oct 11, 2018 Posts 106 Jan 15, 2019 #199 Unfortunately it was run more than one hour in Safe Mode, but nothing has changed...
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 18, 2019 #200 So we've identified the problem (remnants of previous .NET installations), now it's just the matter of removing them from the system.
So we've identified the problem (remnants of previous .NET installations), now it's just the matter of removing them from the system.