[SOLVED] [Server2012R2Upd3 x64] 8024000b and 80240037

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Attempt the August update again and provide the CBS.log if it fails. Thanks.
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Please do the following.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

Apologies for the delay, and thanks again.
Below is the results:

Fix result of Farbar Recovery Scan Tool (x64) Version: 19-08-2017
Ran by administrator (20-08-2017 00:04:39) Run:7
Running from C:\Users\Administrator\Desktop
Loaded Profiles: MediaAdmin$ & administrator (Available Profiles: MediaAdmin$ & administrator & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-bcrypt-primitives-dll_31bf3856ad364e35_none_80110b1421fccd64\6.3]
@="6.3.9600.18154"
"6.3.9600.18298"=-
EndRegEdit:










*****************




====> Registry


==== End of Fixlog 00:04:39 ====
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Please do the following.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

Thanks.

Logs as below:
Fix result of Farbar Recovery Scan Tool (x64) Version: 19-08-2017
Ran by administrator (20-08-2017 05:38:32) Run:8
Running from C:\Users\Administrator\Desktop
Loaded Profiles: MediaAdmin$ & administrator (Available Profiles: MediaAdmin$ & administrator & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18289]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18292]


[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18292_none_49883e56d02ed1e8]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18423_none_49d4f1e0cff521f6]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18438_none_49cf2366cff8bc9a]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18474_none_499fe28ed01cc702]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18589_none_499a15fad0205ecd]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18685_none_499616b8d023f698]


StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\6.3]
@="6.3.9600.18264"
"6.3.9600.18289"=-
EndRegEdit:
*****************


HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18289 => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18292 => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18292_none_49883e56d02ed1e8 => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18423_none_49d4f1e0cff521f6 => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18438_none_49cf2366cff8bc9a => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18474_none_499fe28ed01cc702 => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18589_none_499a15fad0205ecd => key not found.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18685_none_499616b8d023f698 => key not found.


====> Registry


==== End of Fixlog 05:38:33 ====
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Please do the following.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

Thanks.
Log:

Fix result of Farbar Recovery Scan Tool (x64) Version: 19-08-2017
Ran by administrator (20-08-2017 06:14:13) Run:9
Running from C:\Users\Administrator\Desktop
Loaded Profiles: MediaAdmin$ & administrator (Available Profiles: MediaAdmin$ & administrator & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18289]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18292]


[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18292_none_49883e56d02ed1e8]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18423_none_49d4f1e0cff521f6]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18438_none_49cf2366cff8bc9a]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18474_none_499fe28ed01cc702]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18589_none_499a15fad0205ecd]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18685_none_499616b8d023f698]


StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\6.3]
@="6.3.9600.18264"
"6.3.9600.18289"=-
EndRegEdit:
*****************




========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


The operation completed successfully.




========= End of CMD: =========


HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18289 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a\v!6.3.9600.18292 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18292_none_49883e56d02ed1e8 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18423_none_49d4f1e0cff521f6 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18438_none_49cf2366cff8bc9a => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18474_none_499fe28ed01cc702 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18589_none_499a15fad0205ecd => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.3.9600.18685_none_499616b8d023f698 => key removed successfully


====> Registry


==== End of Fixlog 06:14:14 ====
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

We're getting further. Hang in there. Please do the following.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

Thanks again.

Below is the log:
Fix result of Farbar Recovery Scan Tool (x64) Version: 20-08-2017
Ran by administrator (20-08-2017 23:13:16) Run:10
Running from C:\Users\Administrator\Desktop
Loaded Profiles: MediaAdmin$ & administrator (Available Profiles: MediaAdmin$ & administrator & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS


[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\v!6.3.9600.18289]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\v!6.3.9600.18292]


[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18292_none_5ce1c1b58824383a]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18423_none_5d2e753f87ea8848]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18438_none_5d28a6c587ee22ec]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18505_none_5d46179187d8803b]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18589_none_5cf399598815c51f]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18685_none_5cef9a1788195cea]


StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\6.3]
@="6.3.9600.18264"
"6.3.9600.18289"=-
EndRegEdit:




*****************




========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


The operation completed successfully.




========= End of CMD: =========


HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\v!6.3.9600.18289 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.3.9600.18384 (winblue_ltsb.160621-0600)\ComponentFamilies\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_none_2003e93c9ec12938\v!6.3.9600.18292 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18292_none_5ce1c1b58824383a => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18423_none_5d2e753f87ea8848 => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18438_none_5d28a6c587ee22ec => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18505_none_5d46179187d8803b => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18589_none_5cf399598815c51f => key removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.3.9600.18685_none_5cef9a1788195cea => key removed successfully


====> Registry


==== End of Fixlog 23:13:17 ====
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Yes we are making progress. Please do the following.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

Thanks again, below is the log:
Fix result of Farbar Recovery Scan Tool (x64) Version: 20-08-2017
Ran by administrator (21-08-2017 18:10:05) Run:11
Running from C:\Users\Administrator\Desktop
Loaded Profiles: MediaAdmin$ & administrator (Available Profiles: MediaAdmin$ & administrator & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_en-us_cfa933f9c0cb71c0\6.3]
@="6.3.9600.18266"
"6.3.9600.18302"=-
EndRegEdit:




*****************




====> Registry


==== End of Fixlog 18:10:06 ====
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

I have attempted the same August KB again, error again.

Uploaded the cbs log - Download CBS.zip from Sendspace.com - send big files the easy way

Ive just read the log - it's still missing the same file, is that correct?
MissingWinningComponentKey on resource [100]"amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.3.9600.18302_none_065a07bcdd4a3863"[gle=0x80004005]



Thanks.
 
Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Ive just read the log - it's still missing the same file, is that correct?
MissingWinningComponentKey on resource [100]"amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.3.9600.18302_none_065a07bcdd4a3863"[gle=0x80004005]

Nope. The last one we fixed was actually the following.
Code:
amd64_microsoft-[COLOR=#ff0000]windows-i..timezones[/COLOR].resources_31bf3856ad364e35...

Please do the following.

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. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Re: [WinServer2012R2Upd3 x64] 8024000b and 80240037

Hi BrianDrab,

Thanks.

Fix result of Farbar Recovery Scan Tool (x64) Version: 20-08-2017
Ran by administrator (22-08-2017 18:13:58) Run:13
Running from C:\Users\Administrator\Desktop
Loaded Profiles: MediaAdmin$ & administrator (Available Profiles: MediaAdmin$ & administrator & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_none_af76b7f278d145d5\6.3]
@="6.3.9600.18266"
"6.3.9600.18302"=-
EndRegEdit:








*****************




====> Registry


==== End of Fixlog 18:13:58 ====
 

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

Back
Top