[SOLVED] [Win10v1607Build14393 x64] Windows Update

BriKay

BriKay

Member
Joined
Apr 13, 2017
Posts
14
Location
Belleville, IL. USA
I have more errors than I can count. No fixes will work, including the fixer I just downloaded from here..it crashed. I tried a second time, it crashed again. Dism...Illegal Characters. SFC...cant run. Cant install some updates, others will install. Tried to upgrade to 1703, didn't work. Quit at the safe_OS phase (as always) This is a fresh install, that took many hours to install. I tried to clean install 1703..didnt happen. so I put this version of 1607 back on. Its an earlier version and its the only version that will install. I am using an ASUS version x551ma. 64 bit. intel processor. I have nothing installed but the OS. I have been dealing with errors since January. And the bsod problem that came at me out of nowhere...Please help


this is the output text

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-13 20:37:12.583
Microsoft Windows 10 Build 14393 - amd64
Not using a script file.


SFCFix version 3.0.0.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2017-04-13 20:37:31.452
----------------------EOF-----------------------
 
Re: Windows Update

BriKay said:
I have more errors than I can count. No fixes will work, including the fixer I just downloaded from here..it crashed. I tried a second time, it crashed again. Dism...Illegal Characters. SFC...cant run. Cant install some updates, others will install. Tried to upgrade to 1703, didn't work. Quit at the safe_OS phase (as always) This is a fresh install, that took many hours to install. I tried to clean install 1703..didnt happen. so I put this version of 1607 back on. Its an earlier version and its the only version that will install. I am using an ASUS version x551ma. 64 bit. intel processor. I have nothing installed but the OS. I have been dealing with errors since January. And the bsod problem that came at me out of nowhere...Please help


this is the output text

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-13 20:37:12.583
Microsoft Windows 10 Build 14393 - amd64
Not using a script file.


SFCFix version 3.0.0.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2017-04-13 20:37:31.452
----------------------EOF-----------------------
Click to expand...
 
Re: Windows Update

OK, please start with 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 SendSpace and just provide the link here.
 
Re: Windows Update

Please also do the following.

Step#1 - 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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Re: Windows Update

no, the memory hasn't been changed. it is the same that it shipped with. There is no reason for it to be bad, unless it came that way. It is 3 years old this month. It started acting up (bsod) in the 1st week of January. I had never even seen a bsod before then. There has been no slow down. the mem is always 40% used or less. No game playing. just every day normal use. Security alerted me to some malware the day before it started being stupid. I have clean installed, DBAN, inbox formatted. I don't get it. I have had a bad mem test, then a good one, then bad ones. Bad ram wouldn't have a bad test, then a good one.... Bad drivers maybe. (only coming form windows update) I cant change the ram as it is under the mother board. (top opening asus crappy laptop) I cant even remove the battery. I am not ruling out bad ram. but why would it start acting up after malware, when before it was perfect? No errors, updates worked. OS installed fine.... Perplexed.
 
Re: Windows Update

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\4399b6cabcade24f1e6f57a4ff3856e001ac5c9016d64dcbd1944046630c4c5d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\5bcf33a3ea2ad2731a89d1fc18f4f1a495f06a06913cc84ef7336ffd4abe272f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\830bd465ff48d49936cce12868bf0df2dbf5f6ceba05f6ee3cb5aacd6eab3563.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8b4a423be3d515693d6734aa26c43cc2d0ea262266af2ead0ba8c7f8697f3617.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\b19c2574c5a32efdb8a445058649b4ed2c4d3a0440ed820922e121d88d3507fa.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\bcec0b007ad3c04810646b38b3df5604fda1fa7a84215cd9318b59f8eda086e2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c059acf0abf15a64504b6abcc07c2a317e10b29d399ba4557ce15a1b59d6ac8e.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c5e6782b384e5a751756014d7627839f1b5241678dd87771bb536751aa2dc53f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d4850add4e90a3784767c0251f7ec5573f00a5844c61a79d892ee0314863f8bf.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fabb45f5422349070c702e0b66332138de4ab35b1e49fc7b431fafc7dc5cddb6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\185b5e168ed..2233b99fd13_31bf3856ad364e35_10.0.14393.1066_b4c91463e28571f4.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2d3b14b6063..b0489712b24_31bf3856ad364e35_10.0.14393.953_d6d2cc9e1b6a1352.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6ec01c64b54..4993a2e4d4a_31bf3856ad364e35_10.0.14393.953_db8a42b5ead30c53.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8a09ace5181..439b850e3e4_31bf3856ad364e35_10.0.14393.206_cec650657c03e822.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c7e5a054c3..d8fef4ff42f_31bf3856ad364e35_10.0.14393.206_dbd8ef2e42061170.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9d0c52aa6e..151a71aeb3d_31bf3856ad364e35_10.0.14393.351_405f011ed54d83e2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f832dfd73f0..e8e25473b0e_31bf3856ad364e35_10.0.14393.953_a7131c20d2b56cc8.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f8b2f158f3d..b7ac3f2a4e5_31bf3856ad364e35_10.0.14393.1066_96727d588b805f74.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce7d7e05059ff.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce72d7e05059ff.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_52f4fe5ece014b6c76d1bc2b3e61e849_31bf3856ad364e35_10.0.14393.1066_none_2a59e3d2455b3e61.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_7922f2c35178ede8459f78060c0a06df_31bf3856ad364e35_10.0.14393.1066_none_943ea3786119c2d1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b6ad814dcd1b3e168d71e8cf610785f2_31bf3856ad364e35_10.0.14393.1066_none_d5f9597e171434b3.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing3d-winrt-core_31bf3856ad364e35_10.0.14393.1066_none_0bfbfac4d072a9d1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..ty-aadcloudapplugin_31bf3856ad364e35_10.0.14393.1066_none_987daad765588aca.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\4399b6cabcade24f1e6f57a4ff3856e001ac5c9016d64dcbd1944046630c4c5d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\4399b6cabcade24f1e6f57a4ff3856e001ac5c9016d64dcbd1944046630c4c5d.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\5bcf33a3ea2ad2731a89d1fc18f4f1a495f06a06913cc84ef7336ffd4abe272f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\5bcf33a3ea2ad2731a89d1fc18f4f1a495f06a06913cc84ef7336ffd4abe272f.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\830bd465ff48d49936cce12868bf0df2dbf5f6ceba05f6ee3cb5aacd6eab3563.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\830bd465ff48d49936cce12868bf0df2dbf5f6ceba05f6ee3cb5aacd6eab3563.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8b4a423be3d515693d6734aa26c43cc2d0ea262266af2ead0ba8c7f8697f3617.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8b4a423be3d515693d6734aa26c43cc2d0ea262266af2ead0ba8c7f8697f3617.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\b19c2574c5a32efdb8a445058649b4ed2c4d3a0440ed820922e121d88d3507fa.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\b19c2574c5a32efdb8a445058649b4ed2c4d3a0440ed820922e121d88d3507fa.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\bcec0b007ad3c04810646b38b3df5604fda1fa7a84215cd9318b59f8eda086e2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\bcec0b007ad3c04810646b38b3df5604fda1fa7a84215cd9318b59f8eda086e2.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c059acf0abf15a64504b6abcc07c2a317e10b29d399ba4557ce15a1b59d6ac8e.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c059acf0abf15a64504b6abcc07c2a317e10b29d399ba4557ce15a1b59d6ac8e.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c5e6782b384e5a751756014d7627839f1b5241678dd87771bb536751aa2dc53f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c5e6782b384e5a751756014d7627839f1b5241678dd87771bb536751aa2dc53f.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d4850add4e90a3784767c0251f7ec5573f00a5844c61a79d892ee0314863f8bf.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d4850add4e90a3784767c0251f7ec5573f00a5844c61a79d892ee0314863f8bf.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fabb45f5422349070c702e0b66332138de4ab35b1e49fc7b431fafc7dc5cddb6.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fabb45f5422349070c702e0b66332138de4ab35b1e49fc7b431fafc7dc5cddb6.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\185b5e168ed..2233b99fd13_31bf3856ad364e35_10.0.14393.1066_b4c91463e28571f4.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\185b5e168ed..2233b99fd13_31bf3856ad364e35_10.0.14393.1066_b4c91463e28571f4.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2d3b14b6063..b0489712b24_31bf3856ad364e35_10.0.14393.953_d6d2cc9e1b6a1352.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2d3b14b6063..b0489712b24_31bf3856ad364e35_10.0.14393.953_d6d2cc9e1b6a1352.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6ec01c64b54..4993a2e4d4a_31bf3856ad364e35_10.0.14393.953_db8a42b5ead30c53.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6ec01c64b54..4993a2e4d4a_31bf3856ad364e35_10.0.14393.953_db8a42b5ead30c53.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8a09ace5181..4›9b850e3e4_31bf3856ad364e35_10.0.14393.206_cec650657c03e822.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8a09ace5181..439b850e3e4_31bf3856ad364e35_10.0.14393.206_cec650657c03e822.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8a09ace5181..439b850e3e4_31bf3856ad364e35_10.0.14393.206_cec650657c03e822.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c7e5a054c3..d8fef4ff42f_31bf3856ad364í35_10.0.14393.206_dbd8ef2e42061170.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c7e5a054c3..d8fef4ff42f_31bf3856ad364e35_10.0.14393.206_dbd8ef2e42061170.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c7e5a054c3..d8fef4ff42f_31bf3856ad364e35_10.0.14393.206_dbd8ef2e42061170.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9d0c52aa6e..151a71aeb3d_31bf3856ad364o35_10.0.14393.351_405f011ed54d83e.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9d0c52aa6e..151a71aeb3d_31bf3856ad364e35_10.0.14393.351_405f011ed54d83e2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9d0c52aa6e..151a71aeb3d_31bf3856ad364e35_10.0.14393.351_405f011ed54d83e2.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f832dfd73f0..e¸e25473b0e_31bf3856ad364e35_10.0.14393.953_a7131c20d2b56cc8.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f832dfd73f0..e8e25473b0e_31bf3856ad364e35_10.0.14393.953_a7131c20d2b56cc8.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f832dfd73f0..e8e25473b0e_31bf3856ad364e35_10.0.14393.953_a7131c20d2b56cc8.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f8b2f158f3d..b7ac3f2a4e5_31bf3856ad364e35_10.0.14393.1066_96727d588b805f74.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f8b2f158f3d..b7ac3f2a4e5_31bf3856ad364e35_10.0.14393.1066_96727d588b805f74.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce7d7e05059ff.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce7d7e05059ff.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce72d7e05059ff.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce72d7e05059ff.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_52f4fe5ece014b6c76d1bc2b3e61e849_31bf3856ad364e35_10.0.14393.1066_none_2a59e3d2455b3e61.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_52f4fe5ece014b6c76d1bc2b3e61e849_31bf3856ad364e35_10.0.14393.1066_none_2a59e3d2455b3e61.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_7922f2c35178ede8459f78060c0a06df_31bf3856ad364e35_10.0.14393.1066_none_943ea3786119c2d1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_7922f2c35178ede8459f78060c0a06df_31bf3856ad364e35_10.0.14393.1066_none_943ea3786119c2d1.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b6ad814dcd1b3e168d71e8cf610785f2_31bf3856ad364e35_10.0.14393.1066_none_d5f9597e171434b3.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b6ad814dcd1b3e168d71e8cf610785f2_31bf3856ad364e35_10.0.14393.1066_none_d5f9597e171434b3.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing3d-winrt-core_31bf3856ad364e35_10.0.14393.1066_none_0bfbfac4d072a9d1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing3d-winrt-core_31bf3856ad364e35_10.0.14393.1066_none_0bfbfac4d072a9d1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..ty-aadcloudapplugin_31bf3856ad364e35_10.0.14393.1066_none_987daad765588aca.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\4399b6cabcade24f1e6f57a4ff3856e001ac5c9016d64dcbd1944046630c4c5d with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\4399b6cabcade24f1e6f57a4ff3856e001ac5c9016d64dcbd1944046630c4c5d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\5bcf33a3ea2ad2731a89d1fc18f4f1a495f06a06913cc84ef7336ffd4abe272f with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\5bcf33a3ea2ad2731a89d1fc18f4f1a495f06a06913cc84ef7336ffd4abe272f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\830bd465ff48d49936cce12868bf0df2dbf5f6ceba05f6ee3cb5aacd6eab3563 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\830bd465ff48d49936cce12868bf0df2dbf5f6ceba05f6ee3cb5aacd6eab3563.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8b4a423be3d515693d6734aa26c43cc2d0ea262266af2ead0ba8c7f8697f3617 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8b4a423be3d515693d6734aa26c43cc2d0ea262266af2ead0ba8c7f8697f3617.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\b19c2574c5a32efdb8a445058649b4ed2c4d3a0440ed820922e121d88d3507fa with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\b19c2574c5a32efdb8a445058649b4ed2c4d3a0440ed820922e121d88d3507fa.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\bcec0b007ad3c04810646b38b3df5604fda1fa7a84215cd9318b59f8eda086e2 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\bcec0b007ad3c04810646b38b3df5604fda1fa7a84215cd9318b59f8eda086e2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c059acf0abf15a64504b6abcc07c2a317e10b29d399ba4557ce15a1b59d6ac8e with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c059acf0abf15a64504b6abcc07c2a317e10b29d399ba4557ce15a1b59d6ac8e.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c5e6782b384e5a751756014d7627839f1b5241678dd87771bb536751aa2dc53f with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\c5e6782b384e5a751756014d7627839f1b5241678dd87771bb536751aa2dc53f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d4850add4e90a3784767c0251f7ec5573f00a5844c61a79d892ee0314863f8bf with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d4850add4e90a3784767c0251f7ec5573f00a5844c61a79d892ee0314863f8bf.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fabb45f5422349070c702e0b66332138de4ab35b1e49fc7b431fafc7dc5cddb6 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fabb45f5422349070c702e0b66332138de4ab35b1e49fc7b431fafc7dc5cddb6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\185b5e168ed..2233b99fd13_31bf3856ad364e35_10.0.14393.1066_b4c91463e28571f4 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\185b5e168ed..2233b99fd13_31bf3856ad364e35_10.0.14393.1066_b4c91463e28571f4.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2d3b14b6063..b0489712b24_31bf3856ad364e35_10.0.14393.953_d6d2cc9e1b6a1352 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2d3b14b6063..b0489712b24_31bf3856ad364e35_10.0.14393.953_d6d2cc9e1b6a1352.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6ec01c64b54..4993a2e4d4a_31bf3856ad364e35_10.0.14393.953_db8a42b5ead30c53 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6ec01c64b54..4993a2e4d4a_31bf3856ad364e35_10.0.14393.953_db8a42b5ead30c53.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8a09ace5181..439b850e3e4_31bf3856ad364e35_10.0.14393.206_cec650657c03e822 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8a09ace5181..439b850e3e4_31bf3856ad364e35_10.0.14393.206_cec650657c03e822.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c7e5a054c3..d8fef4ff42f_31bf3856ad364e35_10.0.14393.206_dbd8ef2e42061170 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c7e5a054c3..d8fef4ff42f_31bf3856ad364e35_10.0.14393.206_dbd8ef2e42061170.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9d0c52aa6e..151a71aeb3d_31bf3856ad364e35_10.0.14393.351_405f011ed54d83e2 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9d0c52aa6e..151a71aeb3d_31bf3856ad364e35_10.0.14393.351_405f011ed54d83e2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f832dfd73f0..e8e25473b0e_31bf3856ad364e35_10.0.14393.953_a7131c20d2b56cc8 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f832dfd73f0..e8e25473b0e_31bf3856ad364e35_10.0.14393.953_a7131c20d2b56cc8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f8b2f158f3d..b7ac3f2a4e5_31bf3856ad364e35_10.0.14393.1066_96727d588b805f74 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f8b2f158f3d..b7ac3f2a4e5_31bf3856ad364e35_10.0.14393.1066_96727d588b805f74.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce7d7e05059ff with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce72d7e05059ff with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fba248da3ac..d9f75df17b0_31bf3856ad364e35_10.0.14393.206_8bce72d7e05059ff.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_52f4fe5ece014b6c76d1bc2b3e61e849_31bf3856ad364e35_10.0.14393.1066_none_2a59e3d2455b3e61 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_52f4fe5ece014b6c76d1bc2b3e61e849_31bf3856ad364e35_10.0.14393.1066_none_2a59e3d2455b3e61.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_7922f2c35178ede8459f78060c0a06df_31bf3856ad364e35_10.0.14393.1066_none_943ea3786119c2d1 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_7922f2c35178ede8459f78060c0a06df_31bf3856ad364e35_10.0.14393.1066_none_943ea3786119c2d1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b6ad814dcd1b3e168d71e8cf610785f2_31bf3856ad364e35_10.0.14393.1066_none_d5f9597e171434b3 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b6ad814dcd1b3e168d71e8cf610785f2_31bf3856ad364e35_10.0.14393.1066_none_d5f9597e171434b3.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing3d-winrt-core_31bf3856ad364e35_10.0.14393.1066_none_0bfbfac4d072a9d1 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing3d-winrt-core_31bf3856ad364e35_10.0.14393.1066_none_0bfbfac4d072a9d1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..ty-aadcloudapplugin_31bf3856ad364e35_10.0.14393.1066_none_987daad765588aca.
RegistryScript:: directive failed to complete successfully.


Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 29 datablocks.
Finish time: 2017-04-18 14:18:01.979
Script hash: 2eOGTnsx0oX/gLM/X9X0+F6EFhbOo0WSzJ5qVpZq5Ps=
----------------------EOF-----------------------
 
Re: Windows Update

Heat...age...there are many reasons that memory can go bad. It's hardware...hardware can fail. I can tell you based on what I'm seeing that I'm 99% sure it's either bad memory or bad motherboard/processor. Please do the following.

SFC Scan
1. Right-click on the Start button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Re: Windows Update

Not ready for you to try updates yet. Let's fix the following next.

Code: 
Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-coreuicomponents_31bf3856ad364e35_10.0.14393.0_none_711f38a2547dda64\CoreUIComponents.dll do not match actual file [l:20]'CoreUIComponents.dll' :
Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-simsun_31bf3856ad364e35_10.0.14393.0_none_287d8a85866175cb\simsun.ttc do not match actual file [l:10]'simsun.ttc' :
Hashes for file member \SystemRoot\WinSxS\amd64_netfx4-mscorlib_ni_b03f5f7f11d50a3a_4.0.14305.0_none_e40bcb44af383f8c\mscorlib.ni.dll do not match actual file [l:15]'mscorlib.ni.dll' :
Hashes for file member \SystemRoot\WinSxS\amd64_netfx4-presentationframework_b03f5f7f11d50a3a_4.0.14305.0_none_89b61a09017674cf\PresentationFramework.dll do not match actual file [l:25]'PresentationFramework.dll' :

Please do the following.

Step#1 - 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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 
Re: Windows Update

PowerCopy::
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_netfx4-presentationframework_b03f5f7f11d50a3a_4.0.14305.0_none_89b61a09017674cf\PresentationFramework.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_netfx4-mscorlib_ni_b03f5f7f11d50a3a_4.0.14305.0_none_e40bcb44af383f8c\mscorlib.ni.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-font-truetype-simsun_31bf3856ad364e35_10.0.14393.0_none_287d8a85866175cb\simsun.ttc
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-coreuicomponents_31bf3856ad364e35_10.0.14393.0_none_711f38a2547dda64\CoreUIComponents.dll
Successfully copied file C:\Users\bmk65\AppData\Local\niemiro\Archive\Winsxs\amd64_netfx4-presentationframework_b03f5f7f11d50a3a_4.0.14305.0_none_89b61a09017674cf\PresentationFramework.dll to C:\Windows\Winsxs\amd64_netfx4-presentationframework_b03f5f7f11d50a3a_4.0.14305.0_none_89b61a09017674cf\PresentationFramework.dll.
Successfully copied file C:\Users\bmk65\AppData\Local\niemiro\Archive\Winsxs\amd64_netfx4-mscorlib_ni_b03f5f7f11d50a3a_4.0.14305.0_none_e40bcb44af383f8c\mscorlib.ni.dll to C:\Windows\Winsxs\amd64_netfx4-mscorlib_ni_b03f5f7f11d50a3a_4.0.14305.0_none_e40bcb44af383f8c\mscorlib.ni.dll.
Successfully copied file C:\Users\bmk65\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-font-truetype-simsun_31bf3856ad364e35_10.0.14393.0_none_287d8a85866175cb\simsun.ttc to C:\Windows\Winsxs\amd64_microsoft-windows-font-truetype-simsun_31bf3856ad364e35_10.0.14393.0_none_287d8a85866175cb\simsun.ttc.
The file \\?\C:\Windows\Winsxs\amd64_microsoft-windows-coreuicomponents_31bf3856ad364e35_10.0.14393.0_none_711f38a2547dda64\CoreUIComponents.dll is in use and must be replaced over a reboot.
Successfully pended file for replace over reboot: \\?\C:\Windows\Winsxs\amd64_microsoft-windows-coreuicomponents_31bf3856ad364e35_10.0.14393.0_none_711f38a2547dda64\CoreUIComponents.dll
Successfully restored ownership for C:\Windows\Winsxs\amd64_netfx4-presentationframework_b03f5f7f11d50a3a_4.0.14305.0_none_89b61a09017674cf\PresentationFramework.dll
Successfully restored permissions on C:\Windows\Winsxs\amd64_netfx4-presentationframework_b03f5f7f11d50a3a_4.0.14305.0_none_89b61a09017674cf\PresentationFramework.dll
Successfully restored ownership for C:\Windows\Winsxs\amd64_netfx4-mscorlib_ni_b03f5f7f11d50a3a_4.0.14305.0_none_e40bcb44af383f8c\mscorlib.ni.dll
Successfully restored permissions on C:\Windows\Winsxs\amd64_netfx4-mscorlib_ni_b03f5f7f11d50a3a_4.0.14305.0_none_e40bcb44af383f8c\mscorlib.ni.dll
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-font-truetype-simsun_31bf3856ad364e35_10.0.14393.0_none_287d8a85866175cb\simsun.ttc
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-font-truetype-simsun_31bf3856ad364e35_10.0.14393.0_none_287d8a85866175cb\simsun.ttc
PowerCopy:: directive completed successfully.


Reboot:: directive completed successfully.


PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.


PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-coreuicomponents_31bf3856ad364e35_10.0.14393.0_none_711f38a2547dda64\CoreUIComponents.dll
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-coreuicomponents_31bf3856ad364e35_10.0.14393.0_none_711f38a2547dda64\CoreUIComponents.dll
PostRebootRestorePermissions:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 33 datablocks.
Finish time: 2017-04-18 17:10:03.258
----------------------EOF-----------------------
 
Re: Windows Update

Please do the following again.

SFC Scan
1. Right-click on the Start button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Re: Windows Update

i feel like I have an alien invader in my computer. Illegal characters all over the place. It seems like the more we do to fixit, the worse it gets
 

Attachments

Re: Windows Update

That's exactly what happens with bad RAM. You can't fix them fast enough. I fear that there isn't much we can do as it's a hardware problem. Please provide me with an updated components hive.

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 SendSpace and just provide the link here.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top