Installing the latest Win7 Servicing Stack Update KB 4523206 may lock up your PC

Topic

New Reply

Report in from Seff : Since installing the monthly rollup and service stack update on my main Win7 x64 on Friday, the machine booted and ran normally
[See the full post at: Installing the latest Win7 Servicing Stack Update KB 4523206 may lock up your PC]

3 users thanked author for this post.

jburk07, OTtChris, GreatAndPowerfulTech

Reply | Quote

Replies

I do not know whether it is related and might give a direction for a solution, but this year I have had 2 or 3 occasions (I do not remember anymore how many exactly) that on (only) one of my Win7 x64 machines the updates halted at a certain percentage (mostly 67%). It was always the same computer on which it happened. I did troubleshoot it and the only solution that worked was to manually install the cumulative update from the catalogue. All the other updates could be installed with Windows Update (Office 2010, MSRT, .NET), but just not the cumulative update. That one had to be installed manually. A.o. I had tried installing every update separately via Windows Update, but that did not work.

The last time it happened is however already about 4-5 months ago and I have not touched the December updates, because we are at MS-DEFCON 2.

Maybe the solution is to manually install the SSU?

Also, I always restart the computer after installing the SSU, even though Windows Update does not ask for it.

Also, on the same computer I have had 1 or 2 times the situation that the computer would reboot well after installing the Windows Updates, but I got a black screen instead of the login screen after rebooting the next day (i.e. the 2nd reboot after installing the updates). I then restored an image from before the updates, did the updates again, but to be safe not all at the same time but one by one and then everything went fine.

Reply | Quote

No problem after I installed it on Dec.5 on my stand alone Win 7 Pro SP1 X64 rig.

Reply | Quote

Just to update on my situation, it’s semi-resolved. I ran sfc successfully in safe mode but it reported no integrity violations. That was after doing a system restore to a few days before the updates were installed and which didn’t immediately fix things.

Since then there’s been what currently looks like a progressively improving situation. It now boots to desktop but takes about 4 or 5 minutes to do so, lingering only on the “Welcome” screen but, as of this morning, without any black screen between that screen and the desktop appearing. This improvement seems to have come about since I left the machine on a black screen for quite a time rather than forcibly closing it down, and during which the hard drive chuntered away clearly doing something, and with the desktop eventually appearing. It may or may not have been addressing the problem, and it may or may prove to be a false dawn.

My plan is to carry on as usual, I’ve not reinstalled the updates since the system restore, nor am I applying them to my other machine. The likelihood is that I will discuss it with my local repair technician with whom I’ve previously made plans for upgrading both machines including to Windows 10 but possibly having them build a replacement for the affected  machine anyway. If I decide to get that all sorted one way or another during the course of January then I probably won’t touch any further Windows Updates between now and then.

3 users thanked author for this post.

jburk07, OTtChris, woody

Reply | Quote

[GreatAndPowerfulTech]

Self: I’ve seen the same issue on several customer machines over the past year. In each case, uninstalling the 3rd party anti-virus program resolved the ultra slow boot. In one case, with Panda installed then uninstalled. The boot time was reduced by over 90%. If you have a 3rd party AV you might want to try uninstalling it. On some customer PC’s I booted to safe mode and used geek uninstaller to remove the AV program.

GreatAndPowerfulTech

• This reply was modified 5 years, 4 months ago by GreatAndPowerfulTech.

3 users thanked author for this post.

Kaj4strom, jburk07, Seff

Reply | Quote

Thanks GAPT, I had thought of uninstalling MSE as another option if the improvement wasn’t sustained, and your experience suggests it would be a sensible move.

Interestingly, however, after writing my comment above I went out for a couple of hours so switched off the computer as I prefer to do when I’m out for that length of time, and switching it back on when I returned just now it booted straight to desktop in fractionally over a minute – progress indeed. All that remains is for me to learn how to type on the keyboard while my fingers remain firmly crossed!

2 users thanked author for this post.

Microfix, jburk07

Reply | Quote

[EP]

good choice to remove MSE now, Seff
because MS will no longer offer any new MSE definition updates after the 1/14/2020 EOL date

Quote from MS support article 4527878 about MSE:

Will Microsoft Security Essentials (MSE) continue to protect my computer after the end of support?

No, your Windows 7 computer is not protected by MSE after January 14, 2020. MSE is unique to Windows 7 and follows the same lifecycle dates for support

• This reply was modified 5 years, 4 months ago by EP.
• This reply was modified 5 years, 4 months ago by EP.

Reply | Quote

That’s an option I’m considering in the light of that announcement, although I haven’t yet seen conclusive confirmation as to whether withdrawing support includes immediately stopping the release of definition updates (which it hasn’t always done in the past). In any event, if I decide on moving to Windows 10 in January then both the timing of that and the decision over AV protection under Windows 10 become part of the equation. I don’t know, because I haven’t yet looked into it, how well Defender is viewed, or what optimal AV exists beyond Bitdefender which has its supporters here.

Reply | Quote

Hi Seff,

All of my Win7-x64 computers are Group B. Yesterday, after creating a system restore point, I decided to install the November KB4528069 ESU Test Update, and then to install the December SSU and the December SO rollup.

— Installing the November KB4528069 ESU Test Update appeared to do nothing at all, yet it was installed successfully. Yet maybe it does set some stuff in the registry??? Possibly which the new SSU expects to see???

— I then installed the December KB4531786 SSU. It installed successfully. I did not reboot since I manually installed this update and since the update did not ask me to reboot my computer.

— I then installed the December SO rollup KB4530692 which of course required a reboot. On rebooting, KB4530692 performed an expected second reboot before reaching the login screen after it initially installed some of its files.

I have not experienced any reboot issues, slow reboots, or long delays in getting to the login and welcome screens.

Everyone, we are at Defcon 2. I like to test the new updates only after I have made another backup of my computer. This is a prerequisite to do, if you want to be brave like me and test updates while we are not at Defcon 4 or 5. Why? Because in this case even a System Restore will not restore the previous version of a SSU. This is nothing new in terms of the SSUs.

Back to your SSU issues…

You might try booting into Safe Mode and blowing out everything the Windows\Logs\CBS folder and then rebooting normally. You probably will not be able to delete the CBS.log file since it probably will be in use even in Safe Mode. That doesn’t matter since Windows will create a new CBS.log file along with several new and relatively small CAB files after rebooting. Hopefully this will resolve your issues since I suspect that the December SSU is a bit buggy at parsing either lots or large files in the CBS folder, just as some past SSUs have been. I have only eight files in my CBS folder, totaling only 37 MB.

Best regards,

–GTP

 

1 user thanked author for this post.

jburk07

Reply | Quote

I hadn’t associated the issue with KB4523206 until I read the above. I had decided to install November’s security-only updates on Monday.

Installed KB4523206, restarted system although not required and ran sfc. No issues.

Installed KB4525106, restarted the system and ran sfc. No issues.

Installed KB3525233 and restarted the system. At this point, my attention was turned elsewhere so I did not see what preceded the blank screen. Several attempted ctrl-alt del’s and power cycles did not clear the blank screen until the last power cycle appeared to trigger a normal boot sequence. Ran sfc. No issues.

I have a full system backup taken just before KB4523206 but decided to wait several days and clear important work before planning a restore if that turns out to be necessary. In the meantime, I have not risked even logging out from my user account!

Dell Vostro 3750 | 8GB DDR3 | Intel(R) Core(TM) i5-2410M CPU | Crucial 1TB CT1000MX500SSD1
Microsoft Windows 7 Ultimate 6.1.7601 (Service Pack 1) X64
Security-only updates from Microsoft Catalog as guided by Belarc Security Advisor and Master Patch List
0Patch enabled
ESET Internet Security | Malwarebytes | Glasswire Network Security

Reply | Quote

Group A, Win 7×64, Home Premium, AMD.  My service stack number listed is different then KB4523206.  My number is KB4531786.  No problems.  Installed  MSRT but not the .net.  Rollup KB4530734 also installed.  No problems.

Reply | Quote

It looks like you’ve installed the December updates, while we’re discussing the November ones. We’re on DefCon2 for December, installation is premature.

2 users thanked author for this post.

OscarCP, frederik.jacobs.be

Reply | Quote

Yep  your right. 206 was November. Since I’m Group A it was installed.  Nothing happened.  Same with the Dec. stack.  No problem.

Reply | Quote

We have many machines on the K4523206 since a few weeks with no issues reported.
May want to change the title to “last month’s”, I was totally confused as well

1 user thanked author for this post.

woody

Reply | Quote

MAYBE, installing Win7 Servicing Stack Update KB 4523206 did lock up my PC. But, MAYBE it didn’t.  I say this because in retrospect, I had shut down without realizing that the SSU was waiting to be installed, and W7 doesn’t actually shut down until the waiting updates are processed.  (In other words, I had checked the boxes to install everything that was listed, but I understand that an SSU must install by itself and so this 2nd iteration of updating happened in order to install the SSU.)  After that, I got the black screen.  I remember thinking that this was not the normal behavior for the installation of an update because usually there’s a restart.   I waited a long time for a restart to happen, but I concluded that the machine had been turned off (and this may have been the case, since I had originally selected a shut-down).  So, then I powered up and the machine continued on its way, finally producing the login screen and the desktop. Subsequent power-ups have presented no problem.

1 user thanked author for this post.

OTtChris

Reply | Quote

Last Monday:
2 * Win7 Home x64 fully patched
Nov 19 SMQR (KB4525235) – done – restart – OK
Checked the pipe for anything else
Nov 19 Servicing Stack Update (KB4523206) – done – OK
2 previews – untouched
No problems encountered.

Famous last words….

Reply | Quote

Group B, Norton Security (A-V), Win 7 Ult, Z97 4790K

1) Installed all Nov patches and then SSU KB4531786. No problems.
2) Installed Dec IE cumulative KB4530677, all Dec Office 2010 patches. No problems.
3) Have not installed KB4530692 yet.

If I have time this later today, I’ll sacrifice another machine that does not have November patches installed yet. Will install Nov patches, then SSU, then all Dec patches.

For those that encounter problems, could you please post more detail (install order, A-V, etc) so that I can try to duplicate the scenario on the machine above?

Carl

1 user thanked author for this post.

Seff

Reply | Quote

For the November updates that caused my issue, I installed the monthly rollup KB4525235. I restarted when prompted, and waited with the machine inactive for about 30 minutes for the Task Manager performance indicator to settle down (thanks to PK for offering that tip a good while back). Having previously hidden the optional rollup and .net previews, and not having Office on this machine, I was then offered the SSU KB4523206 which I installed. No restart was prompted so I didn’t restart (possibly my mistake), but I did wait around 30 minutes again before using the computer. Everything ran normally including the following day, but the day after that it gave me the black screen on booting up and the long booting saga thus began.

Thanks for your offer to test it out, it will be interesting to see what happens!

Reply | Quote

As noted under the topic for Defcon4 November Updates, on December 8 I installed SSU KB 4523206 after installing Important Updates. Started with the Monthly Rollup and then installed the two checked Office 2010 updates. Did a restart and the SSU popped up, installed it with no apparent issues (*see below). I have Norton AV on my PC and everything is running perfectly, at least up to this point. *One thing to point out, I did see a black screen during the installation/restart process but because I was back and forth from one end of the house to the other I don’t recall where I was updating wise at the time I noticed a delay with a black screen, then resumed in normal fashion. One thing, as I glanced at the black screen, I recall hoping this wasn’t a failed install. So far though all is running good. Win7 Home, 64 bit, Norton AV, GroupA

MacOS iPadOS and sometimes SOS

Reply | Quote

Some of the above posts indicate that the servicing stack was installed after the other November patches. FWIW the MS support pages for the November (and recent previous months as well) patches state that the latest servicing stack should be installed before the patches. I have always followed their procedure and not had any problems, with perhaps one small exception: on a Win 7 Starter machine I installed the servicing stack and then the IE11 patch. The IE11 patch hung before even reaching what I call the 2-step window where step 1 is ‘Initializing Installation’, and step 2 is ‘Installing’ (when both steps are finished you get the restart needed message). After a 20 minute hang ( I believe it was on a box that stated ‘Searching for Updates on this computer’) I cancelled the installation (which took another 5 minutes), rebooted the machine and attempted another install of the IE11 patch. This time the install worked flawlessly.

So, perhaps it’s a good idea to restart after installing the servicing stack (and install it before the other patches) even though the MS support pages for the stack say no restart is required and no restart request appears after the stack installation.

2 users thanked author for this post.

jburk07, SueW

Reply | Quote

[Seff]

In theory you’re right, but installing the SSU updates first requires doing so manually or at least hiding the other updates so as to clear the update process and enable the SSU update to be offered as it won’t be offered if any other update is on offer. This is a nuance that doesn’t seem to have been spotted by MS but it’s a critical one given that only a very small proportion of users will be likely to obtain their updates manually.

• This reply was modified 5 years, 4 months ago by Seff.

1 user thanked author for this post.

jburk07

Reply | Quote

I agree that it’s a nuance and that perhaps some folks won’t catch it, and that’s precisely why I pointed it out! Just trying to help.

3 users thanked author for this post.

jburk07, Myst, SueW

Reply | Quote

Ever since the increased frequency of SSUs over the past several months, the first thing I’ve done (after imaging my computer) is download the latest SSU from the Catalog, install it, restart my computer, and then wait ~ 15 minutes before proceeding. November was no different:

I downloaded KB4523206 (latest SSU, dated 11/11) from the Catalog & installed it, restarted & waited 15 minutes; downloaded Updates KB4525233 (November SO) and KB4525106 (IE11 November Cumulative); and then installed both Updates and then restarted.

I noticed that my computer took about 22 minutes to configure and then restart, longer than usual. It did not configure and restart twice, as it had after installing August’s and October’s SO and IE11 Updates (I didn’t install September’s).

Win 7 SP1 Home Premium 64-bit; Office 2010; Group B (SaS); Former 'Tech Weenie'

6 users thanked author for this post.

jburk07, DrBonzo, Myst, bassmanzam, abbodi86, Microfix

Reply | Quote

Very good advice @SueW to image prior to installing SSU’s (let alone patches)
SSU’s once installed are permanent, we can’t uninstall them.

Windows - commercial by definition and now function...

1 user thanked author for this post.

SueW

Reply | Quote

Microfix wrote:

Very good advice @SueW to image prior to installing SSU’s (let alone patches)
SSU’s once installed are permanent, we can’t uninstall them.

If you do a System Restore Point *before* installing the SSU would you be able to get back to that point if the SSU caused a problem or are still stuck with it?

:W10Pro and W11Pro 22H2

Reply | Quote

Unfortunately, no.

1 user thanked author for this post.

jburk07

Reply | Quote

I installed the Nov updates on 5 Dec (checked ones only) (Windows 7 Home Premium -64-bit).  Then rebooted and installed KB4523206 — then shut down the PC.  Tried to restart later that day and the PC hung up on the log-in Welcome Screen.  Left it alone for over 1/2 hour and it remained stuck on the welcome screen.  Shut it down with power switch and tried to reboot several times with same result.  Booted up in safe mode without problems  — shut it back down again — booted up as normal and all was ok.  That was 7 days ago and have had no more problems.  I don’t expect it makes any difference, but I am running a dual boot PC (Linux Mint 19.2).  After January, Windows is history – and good riddance!

Anvilhead

3 users thanked author for this post.

pandarunnerpt, jburk07, GoneToPlaid

Reply | Quote

I believe there have been anecdotal reports (link supplied by @sb) of a hard restart, starting in safe mode, before a normal restart, over-riding the problem.

2 users thanked author for this post.

jburk07, GoneToPlaid

Reply | Quote

Locked up or not, this topic is late by a month. Stop messing with the November SSU and start messing with the December one instead.

https://support.microsoft.com/en-us/help/4531786/servicing-stack-update-for-windows-7-sp1-and-server-2008-r2-sp1

Regards, VZ

1 user thanked author for this post.

GoneToPlaid

Reply | Quote

[Seff]

Given the nature of the DefCon arrangements, we don’t need to finalise conclusions about the December updates until the end of the month, and in the meantime any continuing issues with the November updates will prove to be immensely useful in formulating those conclusions. It’s only fairly recently that the November updates were recommended for installation, so of course people are still learning all about the consequences of installing them.

• This reply was modified 5 years, 4 months ago by Seff.

1 user thanked author for this post.

jburk07

Reply | Quote

[DrBonzo]

@VZ: I’m not sure I see what the problem is. If the November SSU is an issue, then it’s an issue, and probably not too many folks with said issue are going to move on to the December SSU before resolving to their satisfaction the November SSU. Besides, the title of this thread pertains to the November SSU (even though it says ‘this month’s’)

• This reply was modified 5 years, 4 months ago by DrBonzo.

2 users thanked author for this post.

jburk07, Kirsty

Reply | Quote

Oh, you’re right. A topic on installing KB4523206 is not one on Installing the latest Win7 Servicing Stack Update.

Reply | Quote

On 3 Dec, downloaded KB4523206 from MS Catalog and installed and rebooted. On 5 Dec, installed Nov patches. No problems.

Win 11 Pro 23H2, Office 2024.
Win 10 Pro 64-bit 22H2, Office 2019.
Win 7 Pro 64-bit, Office 2010.
Nethermost of the technically literate.

Reply | Quote

Had an issue(Black Screened) with that for a Windows 7 Nov 2019 Security Only update on a Samsung laptop and looking at the event logs there where many MSE problem signature issues and that may be what some are experiencing. And MSE has been quite flaky over the past 8 months with MSE failing to start on startup or on reboot and if that reboot happens to be a reboot to finish installing a KB/Update then things can get difficult.

I make it a habit to manually create a restore point before downloading and installing from a  Stand Alone installer package from the Windows Update catalog and that’s extra protection for reverting back to a good Known state on Windows after things go bad during the update process.

MSE is gone from the Laptops that were using it and afterwards most of the the remainder of the Nov 2019 Windows 7 Sec Only/IE 11 cumulative, and that SSU, update completed without any issues, even on the Samsung laptop after MSE was uninstalled.

1 user thanked author for this post.

jburk07

Reply | Quote

DrBonzo wrote:

So, perhaps it’s a good idea to restart after installing the servicing stack (and install it before the other patches) even though the MS support pages for the stack say no restart is required and no restart request appears after the stack installation.

That’s what I did (see earlier post). I still experienced a blank screen ‘freeze’ during the KB4525233 installation. I was able to complete the installation more through persistence rather any forensic analysis although until I do a reboot I won’t know if the issue is fully resolved.

Dell Vostro 3750 | 8GB DDR3 | Intel(R) Core(TM) i5-2410M CPU | Crucial 1TB CT1000MX500SSD1
Microsoft Windows 7 Ultimate 6.1.7601 (Service Pack 1) X64
Security-only updates from Microsoft Catalog as guided by Belarc Security Advisor and Master Patch List
0Patch enabled
ESET Internet Security | Malwarebytes | Glasswire Network Security

2 users thanked author for this post.

jburk07, DrBonzo

Reply | Quote

I installed the November service stack after the DEFCON went green, along with the SO and IE11 cumulative updates and a couple of Office 2010 patches. No issues, so far.

Now I am wondering, a little off topic, what could the December service stack be for? We are almost at the end of Win 7 support. Is it for making possible to subscribe to the paid Extended Service beyond EOL? Something I am not interested in doing — and probably I am not the only one here that feels this way.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

1 user thanked author for this post.

jburk07

Reply | Quote

Group B user here

Ran the November updates and didn’t experience any problems. Been following the DEFCON numbers and only updating when we’re at DEFCON 4/5 (unless of course there was a vital need). However, just had a check of my update history and noticed this:

Legend: Update (KB) – Installed On (YYYY/MM/DD)

1. 2019-09 Security Update (KB4474419) – 2019/10/31
2. 2019-09 Monthly Rollup (KB4516065) – 2019/10/31
3. 2019-10 Monthly Rollup (KB4519976) – 2019/11/04
4. Malicious Software Tool (KB890830) – 2019/11/04
5. 2019-09 Stacking Security Update (KB4516655) – 2019/11/05
6. 2019-11 Monthly Rollup (KB4525235) – 2019/12/07
7. 2019-11 Stacking Security Update (KB4523206) – 2019/12/07

Shutdown and booted multiple times since with no issues. As you can see I completely skipped October’s updates (mostly since I didn’t use my PC all that much), but what confuses me is that September SSU; it may be I installed late because it was pulled or recommended not to be installed(?)

In any case, I installed all the updates via Windows Update rather than Microsoft Catalog, and since my PC is a custom build I’m going to go out on a limb and say it may be an issue with specific manufacturers or hardware components that don’t like something with on or other of the updates, but since I only have one Windows 7 machine I can’t be certain. In general, I (have to) reboot after a Rollup, but don’t after an SSU since it doesn’t prompt one

Knowing my luck it’ll black sceen tomorrow

1 user thanked author for this post.

jburk07

Reply | Quote

Since my initial post last evening, I have restored both laptops to before the svc stack update. Before the restore, one of the laptops would hang (no evidence of hd activity). The other would eventually log into the user a/c after 10 to 15 minutes; a couple of times during the long delay, it messed up wireless network (windows could not find wireless network).

Since the restore, both seem to be okay. The 3rd pc, a desktop, seems to have the same problem, although not so pronounced. May do a system restore on it.

I installed the SSU by itself on Dec 6 after installing the Nov rollup as seemed to be the general instruction – clear out the pending updates (Nov rollup in my case). I then restarted each pc about 10 to 15 minutes after installation. All seemed well after the reboot; it was after a cold start/boot that issues started occurring.

There are no AVs on any of the pcs except MSE. I have had no update problems with any of them until now; suppose I have been fortunate although I have no idea what would have happened without advice from this site.

Starting them in safe mode and then in normal mode had no effect. I did use safe mode for system restore.

Will see what happens now.

1 user thanked author for this post.

jburk07

Reply | Quote

Hi,

I haven’t installed any Windows update since September, waiting for the January ‘end’. The only ones I get are for MSE. Some days ago, I also got the black screen afer the ‘welcome’ blue one. After several tests, I came to think it came from MSE. I uninstalled it, and the black screen didn’t appear again. I put Avast in its place and everything is OK.

 

1 user thanked author for this post.

jburk07

Reply | Quote

Strange, I do not see Servicing Stack Update KB 4523206 listed when I checked WU.  All I see is the NET and Quality rollup along with the MSRT and an unchecked Net 4.8.  I have KB4516655 installed in Nov.  Am I supposed to install the SSU before the monthly patches or wait for it to be offered?

Reply | Quote

The SSU has to be installed exclusively (by itself). It won’t show up in the Important update queue until/unless all other pending updates (checked or unchecked) ar installed or hidden.
You can either install or temporarily hide the updates to get the SSU.

It doesn’t require a reboot, but you should reboot anyway, and let it sit 10 minutes after login before installing any other updates.

Reply | Quote

And please understand that KB4523206 is neither desirable nor current nor likely to appear at all. It’s outdated effective December 10th, 2019. There is a phantom debate going on here.

Look out for KB4531786 instead.

1 user thanked author for this post.

amber438

Reply | Quote

We are on DEFCON-2 for Dec updates, do not install yet.. People are discussing Nov. updates. There is no phantom involved.

5 users thanked author for this post.

jburk07, PDX5802, DrBonzo, Myst, SueW

Reply | Quote

I am at this thread because I was having the same problem of hanging with ONE pc, but it is the one that I did not install SSU to yet.

Desktop was fine:
Win 7 Pro x64, Avast
Installed November update KB4525235 on Dec 9, restarted.
SSU KB4523206 showed up, installed.
Have rebooted several times since then, everything ok.

Laptop issues:
Win 7 Pro x64, MSE
Installed November update KB4525235 on Dec 9, restarted.
SSU KB4523206 showed up but I did not install it.
Waited at least an hour before shutting down; everything looked fine.

Yesterday I got back to this laptop and could not get it to start up, hung at welcome screen. Tried several times throughout the day. Safe mode was fine each time. Still had same problems this morning, but this afternoon, it started up fine.

I did not rollback anything.
The SSU is still waiting for install.
In hindsight maybe I should have let it hang for 24 hours instead of 60 minutes before rebooting in safe mode.

2 users thanked author for this post.

jburk07, woody

Reply | Quote

You mentioned the laptop had MSE. Did anything update related to it? Engine? Definitions?

2 users thanked author for this post.

jburk07, woody

Reply | Quote

Yes, missed that — laptop had MSE update KB 2310138 (v 1.307.146.0) on Dec 9 with KB4525235

1 user thanked author for this post.

PKCano

Reply | Quote

I installed it on Dec 5 along with the Nov updates (Group B) and have not had any problem so far either . I currently run Win 7 Pro 64-bit and Bitdefender.

2 users thanked author for this post.

jburk07, SueW

Reply | Quote

I  installed the November updates prior to getting the KB453206 Service stack update on windows update.  It arrived by itself.  Knowing that this should be installed by itself (Thanks to PKCano in a prior posting on the last service stack update), I installed it on my desktop with  Windows 7 Pro  and then rebooted.  It took a while but came up normally.  It also arrived by itself on the laptop.  I then installed it on my laptop with Win 7 pro and rebooted.  It also took a while to come up.  I do not seem to be having the issues mentioned above at this time.  Perhaps I was lucky.

1 user thanked author for this post.

jburk07

Reply | Quote

Many of the postings indicate that the SSU was installed AFTER the monthly rollup CU.  This is the reverse order of the recommendations on this site and, I believe, from MS.  I wonder if there is a connection.  There must be a reason for this order, otherwise it would be optional and not worth mentioning.  I’ve learned to not mess with Mother MS!

I really was hoping to get through the Jan 2020 final W7 updates before I called it quits, but I’m concerned that this may be a problem.  Seems strange that MS continues to pump out SSU’s for W7 that goes eol a month from now!

 

1 user thanked author for this post.

GoneToPlaid

Reply | Quote

Hi all,

So as per Woody’s demand on twitter i come to post here my experience:

Recently i had lockup’s on startup too, but not bad as some others reported here tho.

Anyways, after a few days noticing the PC lagging hard soon after starting it i came to check the processes and found 2 processes named CompatTelRunner.exe running when the PC was almost freezing for me.

Searched a bit the net and found out some articles about this thing but mostly on win10 but the symptoms were matching.

So what i did is the following : task scheduler and disabled the 2 on this picture :

Since this little modification the problem is gone for me, no more freezes or almost locked PC on startup.

( It is also possible to do a .reg modification to stop them )

Today after answering Woody’s post on twitter i looked a bit more into this, it appears that the folders linked to this exe, “C:\Windows\System32\CompatTel” and “C:\Windows\System32\appraiser” were last modified on the 13 November for me, and what happened on the 13 November regarding win updates on my setup ? :

I did not noticed the problem immediately and not linked it to win update as i press the start button of the PC and not always stay in front of it waiting, coming back to pc a bit after, but the days before noticing the problem each time i started the pc and waited i had those locks-up and freezes at the start, up to the 7 Dec when i checked into this a bit more and disabled the tasks scheduled, as seen on the screenshot, last task run on the 7Dec at 5:44 am ( in French but you will get it :p )

While for me it wasn’t big freezes, not lasting long i mean, it seems some can endure it harder, for example : https://www.robvanderwoude.com/tweaks.php#Tweak12

Probably related to the PC specs, not sure what PC specs have those having big issues but might be linked ( mine is not a recent setup but still decent fast, 3770k@4.2Ghz, Intel SSD etc here )

Well, I’m not sure it is the same issue for all others having issues but it might help some so who knows

 

1 user thanked author for this post.

SueW

Reply | Quote

First, most of the updates I’ve done have shown SSU as an option only after doing the November updates .  I’ve just run into a laptop having issues; I initially thought that it was due to a failing HDD, but after getting hands on the unit I found that the SSD was still within life and showed no bad sectors.

I was able to get the system to boot normally again by disabling Windows Updates.  I think.  I did a couple SFCs and chkdsks for good measure, and disabled one hardware item with bad drivers, but the only actionable change I made was disabling wuauserv.

1 user thanked author for this post.

jburk07

Reply | Quote

I think I may have originally posted this comment to the wrong thread (server 2012 thread); it belongs here:

I feel certain that this is due to MSE Security Intelligence Updates, because I install all Microsoft updates as soon as they show up as available, whether on patch Tuesday or the preview updates that come later in the month. But I did not start having the problem of delayed desktops appearing, whether a black screen with pointer that remains for 25 minutes or just the Windows boot screen that always appears when the OS is loading from hard disk with the small spinning circle lasting 20 minutes before showing the desktop screen, until the latest MSE Security Intelligence Updates (version 1.307.###.0) started appearing on or about the ninth of December. That’s when it started, not with any cumulative updates or SSU’s. As far as I can determine from the WER (error reporting) and also the Event Viewer, the delayed appearance of the desktop on boot or reboot is because one or more services enter a hung state when starting during boot. It might be the Wlan service or the EAP service or one of a number of other services that hang when starting on boot up. They are accompanied by ten or more MP telemetry errors, which also points to Microsoft Security Essentials. If you just wait 20-to-30 minutes, the desktop will eventually appear after the OS clears and restarts the hung services. Then everything works fine after that. Windows 7 x64 SP1 both Home Premium and Professional, three different machines.

 

1 user thanked author for this post.

jburk07

Reply | Quote

No problems with KB4523206 here…

Win7 Starter x2 and Win7 Home Premium x1, all with different – oldish versions of Avast Free. I installed the Nov. Rollup KB4525235 as soon as Woody gave the all clear and did the usual restart. Next day after a cold boot I installed the KB4523206 SSU and restarted – all seemed well. I have since cold booted on at least two subsequent days and everything still seems normal.

Can’t help wondering why so many SSUs though…

1 user thanked author for this post.

jburk07

Reply | Quote

KWGuy wrote:

Many of the postings indicate that the SSU was installed AFTER the monthly rollup CU.  This is the reverse order of the recommendations on this site and, I believe, from MS.  I wonder if there is a connection.  There must be a reason for this order, otherwise it would be optional and not worth mentioning.  I’ve learned to not mess with Mother MS!

I really was hoping to get through the Jan 2020 final W7 updates before I called it quits, but I’m concerned that this may be a problem.  Seems strange that MS continues to pump out SSU’s for W7 that goes eol a month from now!

 

I let Windows Update handle things automatically, cliked “check for updates” and it chose to install the CU (2019-11) before the SSU (2019-11).  Only after installing the CU,  then rebooting, then did WU show the SSU was available.  The SSU was not previously showing in the list of updates that had the CU.

Win 7 Pro x64.

So if M$ recommends installing SSU before CU,  why does Windows Update do the opposite?

 

 

Reply | Quote

Gunter Born offers this:
https://borncity.com/win/2016/10/21/windows-updates-fehlende-deinstallation-erzwingen/

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote