Bork Tuesday, Any Problems Yet?

You are welcome, glad to help.

Bo

 

Two Win 10 Pro x64 upgraded from v1703 15063.674 to v1709 16299.19, after disabling security softs. HMPA still disabled, pending clarity on interaction with Exploit Guard.

Both took a long time here, 5 hours, and 8 hours (!) on the older machine.

Still trying to figure out what issues I have. One is that WD icon shows a red cross (seemingly due to MB3 being installed but off on my primary machine, though currently WD panel shows no actions needed. It is indeed off (EAM guards that machine), no RT protections enabled (I run it on-demand only) and set not to start with Windows. May have to reinstall MB3 to see if that gets rid of the red cross on WD.

Also Start is unresponsive sometimes ...

WU Update history has been cleared on both machines. Edit: Probably due to a cleaning tool ...

On second machine, I only see Microsoft Edge and Weather App tiles in Start Menu, so something's up there.

 

Seamless upgrade to 1709. Download and preparation for the upgrade went pretty fast, then installation with a couple of reboots. After 20 min or so it was successfully done.

 

I have this too (though sometimes right-click Start does work), as well as Windows Security Center sometimes opening to just a blue panel, no content.

Restarting doesn't always solve the problem, last time only a hard reboot fixed it.

Don't think it's HMP.A because it is currently disabled, and there would appear to be no conflict, according to this post? https://www.wilderssecurity.com/threads/hitmanpro-alert-beta.394398/page-25#post-2713141

 

This is very annoying. I only have it on my primary machine - I wonder if anyone else is experiencing this.

Also I have recently been offered KB4041994 through WU, only on this machine, but it failed every time with an 0x80070643. Now it is not being offered anymore. Can't find it in the MS Catalog.

 

Hi Paul,

Continued over here - https://www.wilderssecurity.com/thr...ng-to-windows-10-fall-creators-update.397421/

 

I think most everybody got that update immediately after upgrading to FCU. Thats when I got it.

Bo

 

OK, thanks. Downloads OK but install fails with 0x80070643 here, every time (WU history shows 14 fails so far). Same if I try Windows Update MiniTool (which lists it as a 'Critical update').

Apparently it is an update for a video extension called HEVC and is only downloaded in compatible equipment.

WU Troubleshooter does not help.

I wonder why it is not in the MS Catalog.

 

I had to turn AppGuard to OFF for this update to process. Seemed strange but it worked on my system.

 

You're a star, well found! That worked - at last. Very strange, I had AG on 'Allow installs' but that was not enough.

 

Yup, sometimes not enough, so as a rule of thumb, I whenever attempting a new soft installation, always turn Off AppGuard's protection. This way you'll save headaches, corrupted installations and waste of time, etc.

 

Whether relevant to specific issues mentioned here is difficult to determine, but it may be worth noting that upgrading to Windows 10 v1709 sets up a scheduled "WaaSMedic" operation and may delay (block) its implementation for several days following installation of that W10 version. In my own case, for example, implementation of "WaaSMedic" has been blocked until "2017-10-28T08:57:00Z". Individual settings can be seen under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WaasMedic\State and its operational logs are maintained in the C:\Windows\Logs\waasmedic folder.

__
P.S.: I should have mentioned that the scheduled item itself is described as: "Helps recover update-related services to supported configuration." I suppose the essential point is that the normal and usual installation processes for W10 v1709 do not themselves necessarily complete all steps required for supporting all system configurations and related updates. Apparently some further "delayed medication" is also needed, whatever that may imply for usage during the interval.

 

Glad it worked for you too .

 

Something I noticed with W10 is that it takes a few says after updating for things to settle down. Is like Windows doing things in the background like removing unneeded files, deleting KBs that are not needed anymore with the end result of a leaner and more efficient system.

If you put enough attention to the system you can even tell when its doing it. When I first got W10, it came with version 1607, I saw a lot of activity and didn't know why it was. I thought W10 was going to be like that every day but that was because I ddnt know. Now I know what is doing, expect that activity and I also know that is for the better. The activity this time after upgrading to 1709 is being seamless, less noticeable than before but is still going on. For example, yesterday, out of nowhere, free space in the laptop increased about 500MB without me doing anything. That was Windows on its own doing its thing in the background.

Bo

 

Of course some Windows background operations do some good things like those that you mention. But that's not how WaaSMedic states its own purpose. It says it's to help "recover update-related services to supported configuration" and, if that is so, one would expect the sooner it's done the better for all concerned. It's not at all clear why any such WaaSMedic "good medicine" would need to be blocked until several days after all of the normal installation processes have been completed. In my own case, the usual updates and cleanup operations (both foreground and background) have also been completed, but WaaSMedic remains blocked and pending as I've noted.

 

Perhaps there are reasons for that. Perhaps is better to wait a couple of weeks after the computer has been updated to run the task. The work and results are more accurate?

Bo

 

Perhaps or perhaps not. One could put forth almost any surmise as a possible explanation. I only know that delaying a process to "recover update-related services to supported configuration" makes no sense at all to any ratiocination logic with which I've been made familiar ... unless, of course, the updates required for some system configurations aren't actually ready for v1709 implementation yet. With "good ol'" Microsoft, nothing would surprise me.

 

To me, the delay makes sense. Maybe it takes in W10 longer than two weeks to complete applying updates for things to settle down properly. The first few days I had W10, I remember seeing Windows module installer running in task manager all the time, working, specially when doing something light like watching videos or if the laptop was idle, I didn't know what it was and I thought something must be wrong with the laptop, as Disk was pushed close to a 100%. But now I know there was nothing wrong. Actually, what was happening was proper. After a few days, when things settled down, WMI would not run anymore. Next time I updated, I saw something closely similar, it started to make sense. Now, I expect that behavior in the system and if I don't see it, I would think something is gone wrong. Sometimes you can see whats going on reflected in Events in Event viewer. There has been a few times that I see WMI working, and after it finishes, I go to the viewer, and there is the Event, clearly explaining what just happened. You might see that behavior as suspicious, I don't. I just see it as the way things are supposed to be.

Bo

 

I can only say that's truly remarkable reasoning as a basis for concluding that all of what you call "the way things are supposed to be" was and is somehow related to and explains, justifies, or whatever, the above-noted very-specifically dated blockage of a scheduled process to "recover update-related services to supported configuration". However, you're obviously happy with it and so I'll make no further attempt to respond. My initial comment here on the subject was simply a statement of observed fact. Make of it what you will.

 

I knew I left something out, here is what I said with an edit: the way things are supposed to be in order for the computer to be maintained properly.

I am sorry you dont like it but you should know, perhaps most people around see Microsoft with suspicious, but not everyone does. I certainly dont.

I said in another thread the other day, that if I did, I wouldn't use computers or cell phones. If you think MS is the devil, then why use their products. I certainly wouldn't complain about them, I just wouldn't use them.

Bo

 

@XhenEd and I reported this to AppGuard.

 

Just FYI, the explanation from AppGuard support is: 'The update required PowerShell which is a Guarded application. Lowering to install mode doesn’t Un-Guard PowerShell. Lower to Off does Un-Guard PowerShell'.

 

Interesting. Thanks for the info.

 

https://www.computerworld.com/artic...ug-with-patches-that-have-even-more-bugs.html