MWB Blocks Windows 10 Home Cumulative Updates

[RetiredChief]

The only evidence of this that I can present is that, on one of two computers, the September, 2017, and October, 2017, Cumulative Updates faiiled when MWB 3 Premium was running, and were both successful when MWB was exited.

I assume, without any proof, that the MWB settings are identical on both machines; I have not checked this, as I do not know if there is a specific setting that is known to cause update failure. Doe such a setting exist,  or is there some other known reason for such failure? A brief search of the MWB 3 forum did not turn up any related threads.

I have not yet checked the moon phase settings on the two machines to see if one of them might be maladjusted....

[dcollins]

Strange, we've seen no reports of this and I run Windows 10 with MB3 at home. I'd start by making sure you're on the latest version from https://downloads.malwarebytes.com/file/mb3 and if you still have issues, gathering your Windows logs would help us troubleshoot what's going on here.

[RetiredChief]

On 10/11/2017 at 12:16 AM, dcollins said:

Strange, we've seen no reports of this and I run Windows 10 with MB3 at home. I'd start by making sure you're on the latest version from https://downloads.malwarebytes.com/file/mb3 and if you still have issues, gathering your Windows logs would help us troubleshoot what's going on here.

I don't find it strange, as things that are strange are, to me, normal.

Both computers are using MWB 3 Premium 3.2.2.2018. I could update to the newest release, but then would have to wait another month to see if the problem has been alleviated. Meanwhile, I think having logs looked at might be helpful, but which of the many Windows logs are you asking for?

 

[Firefox]

Below is a good start as to what logs can help to see if there is an issue.

Let's try and get some logs first so the team can review them and see if they can tell what may be causing your issues....

1. FIRST: Create and obtain Farbar Recovery Scan Tool (FRST) logs
2. Download FRST and save it to your desktop
   NOTE: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit
3. Double-click to run FRST and when the tool opens click "Yes" to the disclaimer
4. Press the "Scan" button
5. This will product two files in the same location (directory) as FRST: FRST.txt and Addition.txt
   NOTE: These two files will be collected by the MB-Check Tool and added to the zip file for you
6. NEXT: Create and obtain an mb-check log
7. Download MB-Check and save to your desktop
8. Double-click to run MB-Check and within a few second the command window will open, then click "OK"
9. This will produce one log file on your desktop: mb-check-results.zip
10. Attach this file to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area
    

Thank You,

Firefox

[RetiredChief]

Herewith for your entertainment, some light reading.

mb-check-results.zip

[RetiredChief]

I submitted the requested files a week ago; any progress?

[Firefox]

3 minutes ago, RetiredChief said:

I submitted the requested files a week ago; any progress?

@dcollins or @nikhils

[dcollins]

I apologize, this post slipped past me. Unfortunately we need your Windows Update logs to troubleshoot this:

1. Navigate to C:\Windows\Logs
2. Right click WindowsUpdates and choose Send to -> Compressed (Zipped) folder
3. This will create a zip file on your desktop, please upload the zip file here

[RetiredChief]

21 hours ago, dcollins said:

I apologize, this post slipped past me. Unfortunately we need your Windows Update logs to troubleshoot this:

1. Navigate to C:\Windows\Logs
2. Right click WindowsUpdates and choose Send to -> Compressed (Zipped) folder
3. This will create a zip file on your desktop, please upload the zip file here

Since I submitted the files,  I have installed the Windows 10 Fall Creators update. Knowing that the update would take three to four hours, and not being willing to have the update fail if MWB caused that failure, I exited it before starting the update. That left the only Windows Update logs dated 19 and 20 October, after the update. Would those logs be of any use to you, or are we now at a dead end?

If the files are useless, and assuming that there will be a November, 2017, cumulative update,  I could let MWB run while trying to install that update, as cumulative updates don't take nearly as much time as major release updates;  in fact, with MWB running, the failure for the October cumulative update occurred after the 3% preparing-to-install mark was reached, so I lost very little time in getting the update to install. All I had to do was disable MWB and search again for updates; as the update files were already on the computer, it took only a very short time to resume the installation process.

Finally, if you do want the log files from the next cumulative update, at what point should I gather them for you? That is,  assuming that the process were to fail with MWB running, ought I to gather whatever log files there are, or should I exit MWB, proceed with the update, and then gather the files?

[dcollins]

We would need the logs of the failure to diagnose the issue. If it does happen again, gathering the logs after the failure is the best solution.

I didn't have any issue doing the upgrade, but I'll keep testing to see if we can find the issue.

[RetiredChief]

A short while ago, I installed  KB4048955, the November 2017 Cumulative Update for Windows 10, with MWB 3 active. This worked; the problem I reported  was apparently related to the Fall Creators Update. Ergo gluc, as Pantagruel said, until and/or  unless the problem should arise again, I hereby deem that the case is closed.