[SOLVED] Error Code 8007371B

BrianDrab · May 28, 2015

It doesn't appear that you followed the steps from Go The Power as I don't see the requested logs from him. Thank you.

josephus · May 28, 2015

Hi Brian and Alex good evening from Toronto,

You were right, i missed it and just follow your instructions leaving Alex instructions behind by error. My mistake and please accept my apologies. I did not missed the Australian flag but I missed the message.

Anyways, I did follow Alex instructions and for whatever reason I do have now two errors: Code error 8007371b and code error 80073712 (See enclosed picture). Alex in his previous message did expected to fail, but I wasn't expecting a double 'code error' this time around. Those are the files (See the link bellow)

https://www.dropbox.com/s/hsb87xq2jw2fo87/cbs_josephus_28May.txt.rar?dl=0
https://www.dropbox.com/s/z2cx30y8reuo026/Sidebyside?dl=0

And as an attachment the the other one and I include the picture showing the two errors.

Thanks for your efforts

Josephus

Go The Power · May 29, 2015

We have made improvements, the previous fix has repaired one key. We just have a couple more to do.

Please download SystemLook from one of the links below and save it to your Desktop.
Download Mirror #1
Download Mirror #2

Double-click SystemLook.exe to run it.

Copy the content of the following codebox into the main textfield:

Code:

:filefind
*Microsoft-Windows-Security-NTLM*
*Microsoft-Windows-Security-CredSSP*
*Microsoft-Windows-MSAuditEvtLog*
*Microsoft-Windows-Security-Digest*
*Microsoft-Windows-Security-CredSSP*
*Microsoft-Windows-Security-Kerberos*
*Microsoft-Windows-MSAuditEvtLog*
*Microsoft-Windows-Security-Digest*
*Microsoft-Windows-Security-Schannel*
*Microsoft-Windows-ncrypt-dll*
*Microsoft-Windows-MSAuditEvtLog.Resources*
*Microsoft-Windows-ncrypt-dll*
*Microsoft-Windows-MSAuditEvtLog.Resources*
*Microsoft-Windows-LSA.Resources*
*Microsoft-Windows-LSA*
*Microsoft-Windows-Security-NTLM*

Click the Look button to start the scan.
When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.

Note: The log can also be found on your Desktop entitled SystemLook.txt

Code:

2015-05-28 20:21:20, Error                 CSI    00000d14 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #14416364# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024]
2015-05-28 20:21:20, Error                 CSI    00000d15 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #14416363# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024]
2015-05-28 20:21:20, Error                 CSI    00000d16 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #14416362# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150024]
2015-05-28 20:21:20, Error                 CSI    00000d17 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #14416361# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150024]
2015-05-28 20:21:20, Info                  CSI    00000d18 Changelist shadowed missing its manifest - Microsoft-Windows-Security-NTLM, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d19 Changelist shadowed missing its manifest - Microsoft-Windows-Security-Kerberos, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d1a Changelist shadowed missing its manifest - Microsoft-Windows-Security-CredSSP, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d1b Changelist shadowed missing its manifest - Microsoft-Windows-MSAuditEvtLog, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d1c Changelist shadowed missing its manifest - Microsoft-Windows-Security-Digest, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d1d Changelist shadowed missing its manifest - Microsoft-Windows-Security-CredSSP, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d1e Changelist shadowed missing its manifest - Microsoft-Windows-Security-Kerberos, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d1f Changelist shadowed missing its manifest - Microsoft-Windows-MSAuditEvtLog, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d20 Changelist shadowed missing its manifest - Microsoft-Windows-Security-Digest, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d21 Changelist shadowed missing its manifest - Microsoft-Windows-Security-Schannel, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d22 Changelist shadowed missing its manifest - Microsoft-Windows-Security-Schannel, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d23 Changelist shadowed missing its manifest - Microsoft-Windows-ncrypt-dll, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d24 Changelist shadowed missing its manifest - Microsoft-Windows-MSAuditEvtLog.Resources, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d25 Changelist shadowed missing its manifest - Microsoft-Windows-ncrypt-dll, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d26 Changelist shadowed missing its manifest - Microsoft-Windows-MSAuditEvtLog.Resources, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d27 Changelist shadowed missing its manifest - Microsoft-Windows-LSA.Resources, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d28 Changelist shadowed missing its manifest - Microsoft-Windows-LSA, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d29 Changelist shadowed missing its manifest - Microsoft-Windows-LSA, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Info                  CSI    00000d2a Changelist shadowed missing its manifest - Microsoft-Windows-Security-NTLM, Version = 6.1.7601.18714, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-05-28 20:21:20, Error                 CSI    00000d2b@2015/5/29:00:21:20.016 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(935): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]

josephus · May 29, 2015

Hi Alex and good afternoon,

I just completed your instructions and copy the content of your first Code (the one at the top of a second Code). I'm assuming that the second Code is for illustration purposes only.
As requested I'm attaching the founding of the Systemlock in a Notepad called Systemlock.txt.

Thanks. Hope to talk to you soon,

Joseph

Go The Power · Jun 1, 2015

Hi Joseph,

Work has been flat out this past week and my free time will be pretty limited over the next month, I can see some of the registry keys that need fixing. We should hopefully have a reply to you soon.

Alex

BrianDrab · Jun 1, 2015

Hi Joseph -

I'm going to see if I can step in and help. I'm going to take a slightly different approach. 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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Once this is complete, please go ahead and run Windows Update again. It will likely fail at this point. Once it does, please copy the C:\Windows\Logs\CBS\CBS.log to your desktop and then zip/upload to me. Thank you.

Items for your next post
1. SFCFix.txt
2. CBS.log (after attempting Windows Updates)

josephus · Jun 2, 2015

Hi Brian,

Enclosed are the files you requested. I'm also taking the liberty of sending you a file (WindowsUpadate) dated on May 26. The reason I'm sending this one is because I don't know if you have seen it before. The reason I'm attached them (compress .rar) is because the following message: "2015-05-25 15:20:19:596 1272 187c Shutdwn InstallAtShutdown got install progress." is repeated more than 500 times before you got to this one: "2015-05-25 15:20:23:169 3232 18d0 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8007371b"; then and after a few lines goes back to the first one with a time of less than a minutes difference between the first one. Then the sequence is repeated for several lines and, again same line is repeated more than 200 times before it comes the following line: "2015-05-25 15:20:26:117 3232 1bfc Handler FATAL: CBS called Error with 0x8007371b,", then again it comes the first line that it repeats for another 500 lines o so; etc. Overall, that Update text has 1.65MB. This looks to me that this type of files are not normal and because I'm not so sure if I did send this to you I'm sending it right now with the others you had requested.

I know one thing about those things, one is the frustration that someone gets, like me, on seeing issues that are a bit complicated for us to resolve. I'm sure that this is a Microsoft Security issue that the Software Engineers should have been taking care of it when the whole thing started in Windows Vista and I have seen same problem in Windows 7, that's my case, and in Windows 8.

I truly thank you very much for your efforts in resolving this matter. Say Hi to Alex (Go the Power) on my behalf and thank you to both of you.

Josephus

BrianDrab · Jun 2, 2015

Unfortunately what I have tried isn't working. Thanks for the info you provided. Do you happen to have your Windows 7 CD/DVD?

Also, please try the following.

If you don't have your Windows 7 DVD you may be able to reboot your machine and begin tapping F8. On the Advanced Boot Options screen there is usually a Repair Your Computer option which will do the same thing.
Revert Pending Changes
1. Boot into the Windows RE mode: How to use the Windows 7 System Recovery Environment Command Prompt
2. Once the command Window is displayed please follow the below steps.
3. Type notepad into the command prompt and hit enter.
4. Click the File menu in notepad and choose Open. Click on Computer on the left hand side so that you see all the drive letters. You sill see Boot (X:) and likely others. Look for the drive letter that is associated to Local Disk.
5. Once you've identified the driver letter you may cancel out of this screen and close notepad.
6. Now type the following into the Command Prompt replacing C (shown in red) with the drive letter you identified in bullet#4. Note, there is a space after C:\ as well as before the last forward slash.
DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

7. If all goes well you will see the following as the last few lines. Please let me know if you don't.

Code:

Reverting pending actions from the image...
The operation completed. Any revert of pending actions will be attempted after reboot.
The operation completed successfully.

josephus · Jun 2, 2015

Hi Brian and good afternoon from Toronto,

The following image (show bellow) will indicate that I did my best to follow your instructions. Unfortunately did not go well as we expected. Once I had identified the Drive (G) after I went thru the process of reboot the system with Windows 7 DVD and following the instruction as show on bleepingcomputer.com, I found out that on the Image (page 3, Figure 4: System Recovery Options), there was no Windows 7 highlighted as the picture shows. I my case it was blank. I'm assuming that this was irrelevant, but worth mentioning. Successfully, I did reach a point in which I had to choose, on the System Recovery Option (picture 7 on the bleeping computer.com) the 'Command Prompt'. Once there, I type DISM /Image:C:\ /Cleanup-Image /RevertPendingActions; replacing "C" with the letter "G". The rest of it is clear enough that we did not find what we were looking for. The message is very clear:

Error: 87

* The cleanup-image/revertpendingactions options is unknown.
For more information, refer to the help by running help etc. etc....
The DISM log can be found at X:\windows\logs\DIMS\dims.txt *

To make sure that you get a copy of the DIMS.log file, it has been attached to this response.

Thank you for helping me out.

Josephus

BrianDrab · Jun 2, 2015

From your screenshot (which was helpful by the way) I see that you did not put a space after DISM or a space after Cleanup-Image. Please do that and it should run.

josephus · Jun 2, 2015

Hi Brian and good evening from Toronto,

Yes you were right. I should have add the spaces as you indicated.

So, I started all over and this time, the space between the forward sludge and back sludge were put were they belong and the following have been the message or code that appeared after I enter:

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Version 6.1.7601.17514
Image Version: 6.1.7601.18489

The scratch directory size might be insufficient to perform this operation. This can cause an expecting behavior.
Use the /ScratchDir to point out a folder with sufficient scratch space. The recommended size is at least 1024MB.
Reverting pending action from the image .... ....
The operation completed. Any revert of pending actions will be attempted after reboot.
The operation completed successfully.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
After I reboot the system, there were 3 optional updates to download and 6 important updates ready to install. So, at the end of the installation as requested by a message in the system indicating that I need to start my computer for the installation to take effect, I reboot the system. The result were as follows:

Of the three optional updates: 2 of them were uploaded and installed, without a problem. the third one, called Update for Windows 7 for x64 based Systems (KB3061518) failed. Of course being an optional could be that there's no need for it. The 'error code' for this optional update was the same as the previous one (Error code: 80073712) which suppose to have been corrected. The other 6 updates that belongs to "Security Update for Windows 7 for x64-base System" with their own numbers each failed to installed. showing the Error Code as the one we are dealing with.

Is past 11.15pm and its time for me to say good night and I hope to talk to you tomorrow.

Thank you very much for your help.

Josephus

BrianDrab · Jun 2, 2015

No problem. Please send me an updated C:\Windows\Logs\CBS\CBS.log when able. Thanks.

josephus · Jun 2, 2015

Yes Brian, I can do that.

Good night

BrianDrab · Jun 2, 2015

At this point I'm going to suggest doing a Repair install. This will allow you to keep your data and programs and should fix your issue. Are you willing to try this?

josephus · Jun 3, 2015

Hi Brian,

Thanks for your suggestion and I'm wondering if this will, definitely, work. But we should try anything that can put the Windows operating system to work. On the other hand there's a contradiction, inside Microsoft system and it has nothing to do with the work you do and I can assure you that Sysnative is the best in this business of helping people with Windows Operating System's errors. While using Windows programs to find errors in my system, one of them its called "Windows Update Troubleshoot" I found out that there's contradictions between the Update files and the results and the 'Windows Update Troubleshoot'; one is telling me that, after the troubleshooting has completed, that there was a "Windows Update error 0x80073712(2015-0603-T-11_17_57A) Not Fixed. All other errors, were fix (See Image_001 below).

Yesterday, and you already know about it, after "running Windows Update" (of the three optional updates only two were successful) the result was, at the end of the installation process, two errors, Error code 8007371B and Error code 80073712 (see Image_002). I know that Alex (Go the Power) successfully corrected the error because when I contacted Sysnative for the first time we both were together to corrected and out of 89 updates that were downloaded, after he made the corrections, only 6 were not able to be installed and all 6 are related to Windows Security issues.

Other issue that I did encounter yesterday afternoon when for the first time I installed the original Windows 7 Professional DVD that came with my system in the reboot process and with the disc inn, i press F8 making sure that it will reboot from the DVD. I what I did find a message saying "This version of System Recovery Options is not compatible with the Windows you are trying to repair. Try using recovery disc that is compatible with the version of Windows" (see Image _003). After I click OK the system reboot itself from the HD after I did remove the disk. So, to make sure that I could follow the instructions you gave me I did re-start, after putting the CD back the machine, the computer and I let the process to run by itself without the need of "press any Key" and I only have to do was to follow the instructions given by 'bleepingcomputer.com' to reach the point needled to go to the 'recovery-environmental-command-prompt' and from there follow your instructions from point 2 to 6.

What it concerns me is that the message that appeared on the monitor after pressing the F8 Key saying that 'The version of System Recovery Option is not compatible with the Windows you try to repair' (again see image_003). And my question is "Which tools we are going to use for "Repair install"?. Does Sysnative has its own system to do the Repair install you are mentioning?. I know one thing, you and Alex show to be a bit more intelligent than most of Windows Software Engineers who are recommending to re-install Service Pack 1 or do a complete re-installation of Windows because of a few corrupt files in the system that the Software specialist from Microsoft thing that are beyond repair. You and your team can prove them wrong. I cannot uninstall Service Pack 1 from my system because it came pre-install with Windows 7 Professional edition with the DVD (See image_004). I believe that the Repair install that you are recommending it can be done but not with the DVD that I have.

Hope to hear from you soon.

Thanks for your help.

Josephus

BrianDrab · Jun 3, 2015

You would do the repair install using the Windows 7 Professional (Includes Service Pack 1) DVD from the picture you provided above. A good walkthrough on doing this is at the following link.
http://www.sevenforums.com/tutorials/3413-repair-install.html

If you would prefer to wait until Go The Power is available before doing this I won't take offense. He is much more experienced than I am and may be able to get you fixed although it will still likely take much longer than doing the repair install. This is your choice and I'll respect whatever you decide. Just let me know.

josephus · Jun 3, 2015

Hi Brian,

I hope your notice that on that DVD, which came with my computer, on the left side there's a message that clearly says: "For product support, contact the manufacturer of your PC". The way I do interpret this message is that Microsoft is not interested in helping people out, unless you buy the product directly to them. Microsoft gives those DVD's or CD's to computer manufacturers and, most probably, Microsoft have deals with them to making sure that, when we have a problem, we should not contact Microsoft but the manufacture of the computer. I know about this because the first time I had a problem, I contact Microsoft and one of the technicians which was able, with my permission, to take over my computer and, before doing any work, the first thing he did was to go to 'System' and reading that in my product ID there was *****- OEM-*******-***** he knew automatically that Windows 7 Professional was included on my deal to buy the computer. In seen that, he wanted $USA99.00 to solve my problem which I did agree. Unfortunately and after a payment was made, he was not able to solve it and, therefore, his recommendation was to re-install Windows. Of course I did claim a refund and he did had no choice but to give my money back.

Any ways, I will try to do as you say to see if really works, and I will let you know.

Thanks for helping me out,

Josephus

josephus · Jun 3, 2015

Hi Brian,

I went to the site you recommended and I found out that is a bit complicated for me to follow their instructions. There's is to many choices and I'm not so sure which one I should be using to go to the Repair issue. I cannot even print the instructions because, I'm assuming, I have to re-boot the computer to go thru a process and I must need a printing instructions. When, previously, I went to Bleepingcomputer.com, I was able to print the instructions because, and thru those instructions, I was able to go where you wanted me to go.

So, if you don't have any other ideas to go thru, I will wait for "Go the Power" to see if we can reach the end of it.

Thanks for helping me out,

Josephus

BrianDrab · Jun 3, 2015

It's actually fairly straightforward but I agree that article can be daunting. Following is a likely an easier link. You would just start at step#5. Let me know if you would like to try this or if you prefer to wait for Go The Power so I can let him know. Thanks.

https://www.sysnative.com/forums/windows-7-windows-vista-tutorials/3900-place-upgrade-install-windows-windows-7-vista.html

josephus · Jun 3, 2015

Hi Brian,

It looks more straight forward than the previous one, but I could wait for Alex (Go The Power) to follow after you left on. The system works fine and the problem I have at this moment is the Windows Security issue, so I could wait for him. I do remember that last time Go The Power look at it he did mention that he knows were the errors are.So I thank you very much for your work and I shall wait for our good friend Alex. In the meantime, you and Alex can look at the last CBS log file that it was done after I did your last follow up. Maybe is there something that can help you out too.

Thanks.

Josephus

https://www.dropbox.com/s/ozul5wtgzs0j5go/CBS_June3_5pm.rar?dl=0

[SOLVED] Error Code 8007371B

Emeritus

Contributor

Attachments

Senior Administrator, Windows Update Expert, Contributor

Contributor

Attachments

Senior Administrator, Windows Update Expert, Contributor

Emeritus

Attachments

Contributor

Attachments

Emeritus

Contributor

Attachments

Emeritus

Contributor

Emeritus

Contributor

Emeritus

Contributor

Attachments

Emeritus

Contributor

Contributor

Emeritus

Contributor