S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 19, 2019 #81 Search for: 6.2.9200.21728;6.2.9200.21743
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Aug 19, 2019 #82 softwaremaniac said: Search for: 6.2.9200.21728;6.2.9200.21743 Click to expand... Attachments SearchReg.zip 7.2 KB · Views: 2
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 20, 2019 #83 Still looking for the keys.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 21, 2019 #84 Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Attachments fixlist.txt 3.4 KB · Views: 3
Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Aug 22, 2019 #85 softwaremaniac said: When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Click to expand... Attachments Fixlog.zip 1.5 KB · Views: 2
softwaremaniac said: When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Click to expand...
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 22, 2019 #86 Did you modify permissions? It looks like that FRST wasn't able to import the keys...
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Aug 22, 2019 #87 softwaremaniac said: Did you modify permissions? It looks like that FRST wasn't able to import the keys... Click to expand... No, I do not modified any registry or file permissions. I do not remember I do so. And I always start FRST with RUN as Administrator option. Now same install errors Attachments CBSFix.zip 5.3 MB · Views: 0
softwaremaniac said: Did you modify permissions? It looks like that FRST wasn't able to import the keys... Click to expand... No, I do not modified any registry or file permissions. I do not remember I do so. And I always start FRST with RUN as Administrator option. Now same install errors
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 24, 2019 #88 Please retry from Safe Mode with Networking.
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Aug 27, 2019 #89 softwaremaniac said: Please retry from Safe Mode with Networking. Click to expand... Still no luck Attachments Fixlog.zip 1.6 KB · Views: 2
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 27, 2019 #90 SFCFixScript.txt 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.[/list] Attachments SFCFixScript.txt 2.8 KB · Views: 3
SFCFixScript.txt 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.[/list]
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Aug 28, 2019 #91 softwaremaniac said: Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put Code: tags around the log to break up the text.[/list] Click to expand... Code: SFCFix version 3.0.1.0 by niemiro. Start time: 2019-08-28 11:23:49.581 Microsoft Windows Server 2012 - amd64 Using .txt script file at C:\SFCFix\SFCFixScript.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.2.9200.21728_none_89647e7617511c06. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\884458d032d..ea33dc9b43c_31bf3856ad364e35_6.2.9200.21728_27d084af7ee9f939. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.2.9200.21728_none_89647e7617511c06. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\884458d032d..ea33dc9b43c_31bf3856ad364e35_6.2.9200.21728_27d084af7ee9f939. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_0.0.0.0_none_afc4fbdd752b24e5. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.2.9200.21728_none_89647e7617511c06. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\884458d032d..ea33dc9b43c_31bf3856ad364e35_6.2.9200.21728_27d084af7ee9f939. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_0.0.0.0_none_afc4fbdd752b24e5. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect. RegistryScript:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.1.0 by niemiro has completed. Currently storing 4 datablocks. Finish time: 2019-08-28 11:23:49.779 Script hash: FWegqDZ1JZ0JVPkKZ6dJVwItvT5/9afpI5CHCINw5T4= ----------------------EOF-----------------------
softwaremaniac said: Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put Code: tags around the log to break up the text.[/list] Click to expand... Code: SFCFix version 3.0.1.0 by niemiro. Start time: 2019-08-28 11:23:49.581 Microsoft Windows Server 2012 - amd64 Using .txt script file at C:\SFCFix\SFCFixScript.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.2.9200.21728_none_89647e7617511c06. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\884458d032d..ea33dc9b43c_31bf3856ad364e35_6.2.9200.21728_27d084af7ee9f939. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.2.9200.21728_none_89647e7617511c06. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\884458d032d..ea33dc9b43c_31bf3856ad364e35_6.2.9200.21728_27d084af7ee9f939. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_0.0.0.0_none_afc4fbdd752b24e5. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.2.9200.21728_none_89647e7617511c06. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\884458d032d..ea33dc9b43c_31bf3856ad364e35_6.2.9200.21728_27d084af7ee9f939. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_0.0.0.0_none_afc4fbdd752b24e5. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect. RegistryScript:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.1.0 by niemiro has completed. Currently storing 4 datablocks. Finish time: 2019-08-28 11:23:49.779 Script hash: FWegqDZ1JZ0JVPkKZ6dJVwItvT5/9afpI5CHCINw5T4= ----------------------EOF-----------------------
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 28, 2019 #92 Retry updates and attach CBS.log if any fail.
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Aug 29, 2019 #93 softwaremaniac said: Retry updates and attach CBS.log if any fail. Click to expand... Attachments CBS.zip 302.3 KB · Views: 2
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 29, 2019 #94 Please do the following: Retrieve Components Hive 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file. 2. Please copy this file to your desktop. Note: If you receive an error that this file is in-use, simply reboot your computer and try again. 3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop. 4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
Please do the following: Retrieve Components Hive 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file. 2. Please copy this file to your desktop. Note: If you receive an error that this file is in-use, simply reboot your computer and try again. 3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop. 4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Sep 2, 2019 #95 softwaremaniac said: The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply. Click to expand... Spoiler: components file Meet Google Drive – One place for all your files
softwaremaniac said: The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply. Click to expand... Spoiler: components file Meet Google Drive – One place for all your files
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 2, 2019 #96 You did not set the link to public.
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Sep 3, 2019 #97 softwaremaniac said: You did not set the link to public. Click to expand... I think i fixed that. Can you try again?
softwaremaniac said: You did not set the link to public. Click to expand... I think i fixed that. Can you try again?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 3, 2019 #98 Yes, you did! Attachments fixlist.txt 625 bytes · Views: 1
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Sep 4, 2019 #99 softwaremaniac said: Yes, you did! Click to expand... Attachments Fixlog.zip 745 bytes · Views: 1
ankar84 Well-known member Joined May 31, 2019 Posts 119 Location Russia Sep 4, 2019 #100 And updates errors are still here Attachments CBS.zip 1.1 MB · Views: 1