F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 23, 2016 #21 Can be downloaded from sendspace?
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Feb 23, 2016 #22 Yes, thank you for the logs. :dsmile: I will return shortly with instructions once the provided logs have been reviewed.
Yes, thank you for the logs. :dsmile: I will return shortly with instructions once the provided logs have been reviewed.
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Feb 24, 2016 #24 Hello, Please carry out the instructions below. Reattempt installation of the update (KB3042058) afterwards, and let me know if the update installs. Clear Transactional Logfiles Warning: This fix is intended for use on this particular machine. Do not use this fix on any other machine; doing so may cause damage to your Operating System. If you are not the original poster and require assistance, please start your own topic. Click the Windows Start button. Type CMD in the search bar, right-click Command Prompt and click Run as administrator. Copy and paste (right-click the Window + Paste) each bold line below one at a time into the Command Prompt. Press Enter on your keyboard after each line. Type Y and press Enter on your keyboard if prompted, "Are you sure?". Note: Ignore any failure messages. fsutil resource setautoreset true %SystemDrive%\ attrib -r -s -h %SystemRoot%\System32\Config\TxR\* del %SystemRoot%\System32\Config\TxR\* attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* del %SystemRoot%\System32\SMI\Store\Machine\*.tm* del %SystemRoot%\System32\SMI\Store\Machine\*.blf del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms
Hello, Please carry out the instructions below. Reattempt installation of the update (KB3042058) afterwards, and let me know if the update installs. Clear Transactional Logfiles Warning: This fix is intended for use on this particular machine. Do not use this fix on any other machine; doing so may cause damage to your Operating System. If you are not the original poster and require assistance, please start your own topic. Click the Windows Start button. Type CMD in the search bar, right-click Command Prompt and click Run as administrator. Copy and paste (right-click the Window + Paste) each bold line below one at a time into the Command Prompt. Press Enter on your keyboard after each line. Type Y and press Enter on your keyboard if prompted, "Are you sure?". Note: Ignore any failure messages. fsutil resource setautoreset true %SystemDrive%\ attrib -r -s -h %SystemRoot%\System32\Config\TxR\* del %SystemRoot%\System32\Config\TxR\* attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* del %SystemRoot%\System32\SMI\Store\Machine\*.tm* del %SystemRoot%\System32\SMI\Store\Machine\*.blf del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 24, 2016 #25 I followed the instructions. Some command like del %SystemRoot%\System32\SMI\Store\Machine\*.blf and del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms failed because they don't find files. Update has failed the same. What can I do?
I followed the instructions. Some command like del %SystemRoot%\System32\SMI\Store\Machine\*.blf and del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms failed because they don't find files. Update has failed the same. What can I do?
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Feb 25, 2016 #27 Hello, Whilst I appreciate it may appear we haven't made any progress, there are still steps we can take to troubleshoot this issue. Thank you for your patience thus far. Please carry out the instructions below. Ensure you do not try to install updates afterwards. Farbar Recovery Scan Tool (FRST) Script Please download Farbar Recovery Scan Tool (x64) and save the file to your Desktop. Download View attachment Fixlist.txt and save the file to your Desktop. Important: The file must be saved in the same location as FRST64.exe. NOTICE: This script is intended for use on this particular machine. Do not use this script on any other machine; doing so may cause damage to your Operating System. Right-Click FRST64.exe and select Run as administrator to run the programme. Click Fix. A log (Fixlog.txt) will open on your desktop. Copy the contents of the log and paste in your next reply.
Hello, Whilst I appreciate it may appear we haven't made any progress, there are still steps we can take to troubleshoot this issue. Thank you for your patience thus far. Please carry out the instructions below. Ensure you do not try to install updates afterwards. Farbar Recovery Scan Tool (FRST) Script Please download Farbar Recovery Scan Tool (x64) and save the file to your Desktop. Download View attachment Fixlist.txt and save the file to your Desktop. Important: The file must be saved in the same location as FRST64.exe. NOTICE: This script is intended for use on this particular machine. Do not use this script on any other machine; doing so may cause damage to your Operating System. Right-Click FRST64.exe and select Run as administrator to run the programme. Click Fix. A log (Fixlog.txt) will open on your desktop. Copy the contents of the log and paste in your next reply.
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 25, 2016 #28 Here it is: Fix result of Farbar Recovery Scan Tool (x64) Version:24-02-2016 Ran by user (2016-02-25 21:57:49) Run:1 Running from C:\Users\user\Desktop Loaded Profiles: user (Available Profiles: user) Boot Mode: Normal ============================================== fixlist content: ***************** cmd: sc config trustedinstaller start=auto cmd: net start trustedinstaller cmd: fsutil resource setautoreset true %SystemDrive%\ cmd: attrib -r -s -h %SystemRoot%\System32\Config\TxR\* cmd: echo y | del %SystemRoot%\System32\Config\TxR\* cmd: attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.tm* cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.blf cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms EmptyTemp: ***************** ========= sc config trustedinstaller start=auto ========= DESCRIZIONE: Modifica una voce di servizio nel Registro di sistema e nel database del servizio. SINTASSI: sc <server> config [nome servizio] <opzione1> <opzione2>... OPZIONI: NOTA: il nome dell'opzione include il segno di uguale. � necessario inserire uno spazio tra il segno di uguale e il valore. type= <own|share|interact|kernel|filesys|rec|adapt> start= <boot|system|auto|demand|disabled|delayed-auto> error= <normal|severe|critical|ignore> binPath= <NomePercorsoBinario> group= <GruppoOrdineCaricamento> tag= <yes|no> depend= <Dipendenze (separate da / (barra))> obj= <NomeAccount|NomeOggetto> DisplayName= <nome visualizzato> password= <password> ========= End of CMD: ========= ========= net start trustedinstaller ========= Servizio richiesto gi� avviato. Ulteriori informazioni sono disponibili digitando NET HELPMSG 2182. ========= End of CMD: ========= ========= fsutil resource setautoreset true %SystemDrive%\ ========= Operazione completata. ========= End of CMD: ========= ========= attrib -r -s -h %SystemRoot%\System32\Config\TxR\* ========= ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\Config\TxR\* ========= C:\windows\System32\Config\TxR\*, Procedere con l'operazione (S/N)? y C:\windows\System32\Config\TxR\*, Procedere con l'operazione (S/N)? ========= End of CMD: ========= ========= attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* ========= ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.tm* ========= ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.blf ========= Impossibile trovare C:\windows\System32\SMI\Store\Machine\*.blf ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms ========= Impossibile trovare C:\windows\System32\SMI\Store\Machine\*.regtrans-ms ========= End of CMD: ========= EmptyTemp: => 7.1 GB temporary data Removed. The system needed a reboot. ==== End of Fixlog 22:00:02 ==== please note that system after this fix has been restarted
Here it is: Fix result of Farbar Recovery Scan Tool (x64) Version:24-02-2016 Ran by user (2016-02-25 21:57:49) Run:1 Running from C:\Users\user\Desktop Loaded Profiles: user (Available Profiles: user) Boot Mode: Normal ============================================== fixlist content: ***************** cmd: sc config trustedinstaller start=auto cmd: net start trustedinstaller cmd: fsutil resource setautoreset true %SystemDrive%\ cmd: attrib -r -s -h %SystemRoot%\System32\Config\TxR\* cmd: echo y | del %SystemRoot%\System32\Config\TxR\* cmd: attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.tm* cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.blf cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms EmptyTemp: ***************** ========= sc config trustedinstaller start=auto ========= DESCRIZIONE: Modifica una voce di servizio nel Registro di sistema e nel database del servizio. SINTASSI: sc <server> config [nome servizio] <opzione1> <opzione2>... OPZIONI: NOTA: il nome dell'opzione include il segno di uguale. � necessario inserire uno spazio tra il segno di uguale e il valore. type= <own|share|interact|kernel|filesys|rec|adapt> start= <boot|system|auto|demand|disabled|delayed-auto> error= <normal|severe|critical|ignore> binPath= <NomePercorsoBinario> group= <GruppoOrdineCaricamento> tag= <yes|no> depend= <Dipendenze (separate da / (barra))> obj= <NomeAccount|NomeOggetto> DisplayName= <nome visualizzato> password= <password> ========= End of CMD: ========= ========= net start trustedinstaller ========= Servizio richiesto gi� avviato. Ulteriori informazioni sono disponibili digitando NET HELPMSG 2182. ========= End of CMD: ========= ========= fsutil resource setautoreset true %SystemDrive%\ ========= Operazione completata. ========= End of CMD: ========= ========= attrib -r -s -h %SystemRoot%\System32\Config\TxR\* ========= ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\Config\TxR\* ========= C:\windows\System32\Config\TxR\*, Procedere con l'operazione (S/N)? y C:\windows\System32\Config\TxR\*, Procedere con l'operazione (S/N)? ========= End of CMD: ========= ========= attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* ========= ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.tm* ========= ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.blf ========= Impossibile trovare C:\windows\System32\SMI\Store\Machine\*.blf ========= End of CMD: ========= ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms ========= Impossibile trovare C:\windows\System32\SMI\Store\Machine\*.regtrans-ms ========= End of CMD: ========= EmptyTemp: => 7.1 GB temporary data Removed. The system needed a reboot. ==== End of Fixlog 22:00:02 ==== please note that system after this fix has been restarted
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 26, 2016 #29 1) I checked and there are a lot of updates that fails every day. Each time I shut down, before shutting down it tries to install updates.... 2) OS is in italian... maybe that some commands aren't executing , for example when they require a confirmation (Y/N)?
1) I checked and there are a lot of updates that fails every day. Each time I shut down, before shutting down it tries to install updates.... 2) OS is in italian... maybe that some commands aren't executing , for example when they require a confirmation (Y/N)?
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Feb 26, 2016 #30 Hello, Please repeat the FRST script instructions, only this time using the following script: View attachment Fixlist.txt Provide Fixlist.txt in your next reply. Thank you.
Hello, Please repeat the FRST script instructions, only this time using the following script: View attachment Fixlist.txt Provide Fixlist.txt in your next reply. Thank you.
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 27, 2016 #31 here it is FixIng.txt not fixlist.txt has not been generated Attachments Fixlog.txt 3.8 KB · Views: 4
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 27, 2016 #32 I mean that FixLog.txt has been generated and not FixList.txt. Previous message has been written with smarphone and smartphone keyboard sometimes writes what it want.... and sometimes is amazing....
I mean that FixLog.txt has been generated and not FixList.txt. Previous message has been written with smarphone and smartphone keyboard sometimes writes what it want.... and sometimes is amazing....
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Feb 28, 2016 #33 Hello, I mean that FixLog.txt has been generated and not FixList.txt. Click to expand... That's fine. Fixlog.txt is the resulting log from executing the Fixlist.txt script. Please do the following: Farbar Recovery Scan Tool (FRST) Script Download View attachment Fixlist.txt and save the file to your Desktop. Important: The file must be saved in the same location as FRST64.exe. NOTICE: This script is intended for use on this particular machine. Do not use this script on any other machine; doing so may cause damage to your Operating System. Right-Click FRST64.exe and select Run as administrator to run the programme. Click Fix. A log (Fixlog.txt) will open on your desktop. Copy the contents of the log and paste in your next reply.
Hello, I mean that FixLog.txt has been generated and not FixList.txt. Click to expand... That's fine. Fixlog.txt is the resulting log from executing the Fixlist.txt script. Please do the following: Farbar Recovery Scan Tool (FRST) Script Download View attachment Fixlist.txt and save the file to your Desktop. Important: The file must be saved in the same location as FRST64.exe. NOTICE: This script is intended for use on this particular machine. Do not use this script on any other machine; doing so may cause damage to your Operating System. Right-Click FRST64.exe and select Run as administrator to run the programme. Click Fix. A log (Fixlog.txt) will open on your desktop. Copy the contents of the log and paste in your next reply.
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Feb 29, 2016 #34 Here it is: Fix result of Farbar Recovery Scan Tool (x64) Version:24-02-2016 Ran by user (2016-02-29 13:14:05) Run:3 Running from C:\Users\user\Desktop Loaded Profiles: user (Available Profiles: user) Boot Mode: Normal ============================================== fixlist content: ***************** C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms EmptyTemp: ***************** Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms" => Scheduled to move on reboot. EmptyTemp: => 145.9 MB temporary data Removed. Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 2016-02-29 13:21:42) "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms" => Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms" => Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms" => Could not move C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms => Is moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms => Is moved successfully "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf" => Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf" => Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms" => Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms" => Could not move ==== End of Fixlog 13:21:43 ==== I see that there are several files that cannot be moved. Perhaps this the reason of update failures?
Here it is: Fix result of Farbar Recovery Scan Tool (x64) Version:24-02-2016 Ran by user (2016-02-29 13:14:05) Run:3 Running from C:\Users\user\Desktop Loaded Profiles: user (Available Profiles: user) Boot Mode: Normal ============================================== fixlist content: ***************** C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms EmptyTemp: ***************** Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms" => Scheduled to move on reboot. Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms" => Scheduled to move on reboot. EmptyTemp: => 145.9 MB temporary data Removed. Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 2016-02-29 13:21:42) "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms" => Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms" => Could not move "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms" => Could not move C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms => Is moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms => Is moved successfully "C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf" => Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf" => Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms" => Could not move "C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms" => Could not move ==== End of Fixlog 13:21:43 ==== I see that there are several files that cannot be moved. Perhaps this the reason of update failures?
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Feb 29, 2016 #35 Hello, Please do the following: FRST Recovery Environment Script Note: You require access to a USB drive. Note: Please print off these instructions, or ensure you have access to them using a different device. Insert your USB drive into your computer. Please download Farbar Recovery Scan Tool (x64) to your USB drive. Please download View attachment Fixlist.txt to your USB drive. Enter the Recovery Environment by choosing one of the options below. Option #1: Enter Recovery Environment (Windows 7/Vista) Restart your computer. As soon as the BIOS is loaded begin tapping the F8 key until the Advanced Boot Options appears. Use the arrow keys to select the Repair your computer menu item. Select your the keyboard language settings, and then click Next. Select the operating system you wish to repair, and then click Next. Select your user account, and then click Next. Option #2: Enter Recovery Environment (Windows Installation Disc) Insert your Windows installation disc. Restart your computer. Configure your computer to boot from CD/DVD. Instructions on how to do this can be found here. If prompted, press any key to start Windows from the installation disc. Click Repair your computer. Select English as the keyboard language settings, and then click Next. Select the Operating System you want to repair, and then click Next. Select your user account, and then click Next. Advanced Boot Options Menu Select Command Prompt. In the command window type notepad and press Enter on your keyboard. Notepad will open. Click File followed by Open. Click Computer,write down your USB drive letter on a piece of paper and close Notepad. Type: x:\frst64.exe in the command window. . Note: Replace letter x with the drive letter of your USB drive you wrote down earlier. Press Enter on your keyboard. The tool will start to run. When the tool opens click Yes to the disclaimer. Click Fix. A log (Fixlog.txt) will be created on your USB drive. Copy the contents of Fixlog.txt and paste in your next reply
Hello, Please do the following: FRST Recovery Environment Script Note: You require access to a USB drive. Note: Please print off these instructions, or ensure you have access to them using a different device. Insert your USB drive into your computer. Please download Farbar Recovery Scan Tool (x64) to your USB drive. Please download View attachment Fixlist.txt to your USB drive. Enter the Recovery Environment by choosing one of the options below. Option #1: Enter Recovery Environment (Windows 7/Vista) Restart your computer. As soon as the BIOS is loaded begin tapping the F8 key until the Advanced Boot Options appears. Use the arrow keys to select the Repair your computer menu item. Select your the keyboard language settings, and then click Next. Select the operating system you wish to repair, and then click Next. Select your user account, and then click Next. Option #2: Enter Recovery Environment (Windows Installation Disc) Insert your Windows installation disc. Restart your computer. Configure your computer to boot from CD/DVD. Instructions on how to do this can be found here. If prompted, press any key to start Windows from the installation disc. Click Repair your computer. Select English as the keyboard language settings, and then click Next. Select the Operating System you want to repair, and then click Next. Select your user account, and then click Next. Advanced Boot Options Menu Select Command Prompt. In the command window type notepad and press Enter on your keyboard. Notepad will open. Click File followed by Open. Click Computer,write down your USB drive letter on a piece of paper and close Notepad. Type: x:\frst64.exe in the command window. . Note: Replace letter x with the drive letter of your USB drive you wrote down earlier. Press Enter on your keyboard. The tool will start to run. When the tool opens click Yes to the disclaimer. Click Fix. A log (Fixlog.txt) will be created on your USB drive. Copy the contents of Fixlog.txt and paste in your next reply
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Mar 2, 2016 #36 at the end maybe no error at all: Fix result of Farbar Recovery Scan Tool (x64) Version:02-03-2016 Ran by SYSTEM (2016-03-02 15:04:44) Run:5 Running from h:\ Boot Mode: Recovery ============================================== fixlist content: ***************** C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms ***************** C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf => moved successfully C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf => moved successfully C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms => moved successfully ==== End of Fixlog 15:04:44 ==== and now, what I have to do? Thank you very much
at the end maybe no error at all: Fix result of Farbar Recovery Scan Tool (x64) Version:02-03-2016 Ran by SYSTEM (2016-03-02 15:04:44) Run:5 Running from h:\ Boot Mode: Recovery ============================================== fixlist content: ***************** C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms ***************** C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf => moved successfully C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf => moved successfully C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms => moved successfully C:\windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms => moved successfully ==== End of Fixlog 15:04:44 ==== and now, what I have to do? Thank you very much
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Mar 2, 2016 #37 Tried to update by using windows update but 31 updates failed same error: 80071A91 And also some error 8002024D What can l do? Thanks
Tried to update by using windows update but 31 updates failed same error: 80071A91 And also some error 8002024D What can l do? Thanks
L LiquidTension Windows Update Analyst, Security Analyst Joined Apr 7, 2015 Posts 1,171 Mar 2, 2016 #38 Hello, Run this Microsoft FixIt in aggressive mode: Windows Update Broken? Fix it! << Tech – for Everyone Then run Windows Update and check for updates. This could take a while - please be patient. Provide the names (KB numbers) of a few updates.
Hello, Run this Microsoft FixIt in aggressive mode: Windows Update Broken? Fix it! << Tech – for Everyone Then run Windows Update and check for updates. This could take a while - please be patient. Provide the names (KB numbers) of a few updates.
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Mar 2, 2016 #39 Ok. I have runned the fix. Now I'm awaiting for checking for updates. Before the fix I have runned WURT
Ok. I have runned the fix. Now I'm awaiting for checking for updates. Before the fix I have runned WURT
F frankge973 Active member Joined Feb 15, 2016 Posts 34 Mar 2, 2016 #40 I re used the windows update after the fix. It fails. Again. Enclosed kbs that fail. What can I have to do ? I'm very upset. Attachments Screenshot_2016-03-03-00-39-03.png 409.9 KB · Views: 9 Screenshot_2016-03-03-00-38-39.png 357 KB · Views: 4
I re used the windows update after the fix. It fails. Again. Enclosed kbs that fail. What can I have to do ? I'm very upset.