Replies

@sb Hi Susan, earlier you said “Click to Run – I’m still investigating if [Office issues with April updates] impact you.”

So do you know yet if this is impacting Click-to-Run as well? Thanks

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Also @Ed:

I also held back March security only 4088878 because it was not clear what to do, but I didn’t feel comfortable not having any March and April security updates installed.
Then I read PKCano’s post #185318 on April 17. It’s a simple sum up for Group B that did not uninstall Jan & Feb security updates.
I followed his advice exactly and 0ne week later everything’s still fine.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Does anyone know: when InSpectre disables Meltdown(or Spectre) protection, will that protect against Total Meltdown as well??

Just curious…

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Don’t you read ‘the news’? Woody explained it all Total Meltdown (not Meltdown!) exploit now available

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Let me quote myself to show my Group B pc is humming happily:

TJ wrote:

woody wrote:

KB 4100480 does plug the hole. But it also has lots of problems.

Well, that probably depends on your pc’s current state (of updates). I’m in Group B and was updated to February security only KB 4074587 when I installed 4100480 on April 1st. Never had a problem. (I did NOT uninstall dec/jan/feb before doing that.) I then followed PKCano’s advice on April 17 (see #185318): install 4099950 > reboot > 4088878 > 4093108 > reboot > everything’s Hunky Dory.

So I’m not noticing any side-effects from 4093108.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Thanks Susan.

Susan Bradley wrote:

I have Office 365 personal as well and didn’t have that issue with non saving Outlook credentials. I have not found any documentation that mandates monthly.

Well, I tried your hack

Navigate to “C:\Program Files\Common Files\Microsoft Shared\ClickToRun>”
Run the following command to change the desired channel, let’s say Monthly Channel “OfficeC2RClient.exe /changesetting Channel=Deferred”
Then type in:  OfficeC2RClient.exe /update user

but that didn’t work for my version Office Personal. We talked already about it in post  https://www.askwoody.com/forums/topic/3rd-party-office-365-and-c2r-update-channel-mess-2/ 4 weeks ago.

 

 

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Susan Bradley wrote:

The way c2r folks handle “updates” is by temp turning off the c2r and then when everything looks okay, turning it back on. 

That’s the way I handle it the past two months.

I still recommend that you flip yourself off of the monthly c2r and onto the slower deferred channel (holler if you need help doing that).

I tried your cmd-hack, remember? But that didn’t go well. Turns out we’re on Office 365 Personal, which is hooked onto the Monthly Channel. Any tempering with channels results in messed up log ons.

On my click to run at home with April updates, everything I need working is working so I’d say install.

Thanks, I will

March 27 office updates or March 27 windows updates?

Office. I’m ok with the Windows updates.

Edit: It’s getting late here on the other side of the ocean. Need to get some sleep.
Thanks Susan if you can answer my question about the March Office updates. Will respond tomorrow.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

P.S. I’m on a 64-bit machine. Thank for clarifying that to others @twbartender.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

1 user thanked author for this post.

twbartender

woody wrote:

KB 4100480 does plug the hole. But it also has lots of problems.

Well, that probably depends on your pc’s current state (of updates).
I’m in Group B and was updated to February security only KB 4074587 when I installed 4100480 on April 1st. Never had a problem.
(I did NOT uninstall dec/jan/feb before doing that.)

I then followed PKCano’s advice on April 17 (see #185318):  install 4099950 > reboot > 4088878 > 4093108 > reboot > everything’s Hunky Dory.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

2 users thanked author for this post.

Chessie, OscarCP

Hi @sb,

I understand that there is no Defcon for Click-to-run versions because in your Master Patch List you write “… These updates will only be released for volume license versions.  All Office 365 releases are on the click to run model that install silently and in the background.”
However, I assume the silent Click-to-run updates will have the same or comparable updates as the ones for Office 2016. So if the Office 2016 April updates are said to be ‘Safe to install’, then the Click-to-run April updates should be safe to install as well.
Is that correct?

And what about the March(27) updates?

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Was a one time donator till now, and will become a steady Patron.

Why? Because thanks to you/ @Woody, @MrBrian, @PKCano, @sb and many loungers my Group B pc is humming like a bird – despite MS’s mess ups.

Join the club, folks! Donate or become a patron for only a couple of bucks a month.
It seems you even get free benefits from the Dalai Lama!

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

3 users thanked author for this post.

Elly, woody, jburk07

Like the man said: Helps to unmuddy the water a bit. I would even say ‘a lot’.

Held off any updates (or uninstalls) for more than a month. Just couldn’t keep up with all the patches and repatches, but now I was ready to give it a try – thanks to @MrBrian’s sum up.

Had IE 4092946 and 4100480 already installed, and that turned out to be no issue when I just installed 4099950 > reboot > 4088878 > 4093108 > reboot.
Everything’s working fine – for now.

Thank you again & always @Woody @sb @MrBrian @PKCano!

 

 

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

2 users thanked author for this post.

JDeC, MrBrian

Didn’t install any updates (except KB41000480) since February on my Group B pc (and don’t plan to do so till things get cleared up), but today I noticed something else:

I took a lot longer than usual for my pc to get ready, and as I expected it was because of my AV.
Its log showed that it had prevented an unauthorized connection attempt by conhost.exe, that a new firewall rule had been made for Outgoing UDP Ports 137 and 138 and that firewall rules has been updated Furthermore a new shortlink of the AV had appeared on my desktop (which only occurs when the engine is updated).
So my guess is, that [something] is coordinated between MS and the AV.

Can anyone here clarify what’s going on?

(Note to TS: the tag that was showing in the field below my text pane read “2012 April Rollup”. Typo?)

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

You are totally right. Must be the wisdom of age speaking.
I’d better catch up on that subject: almost a pensioner myself!
(And stop reading so many AskWoody Horror Stories  ;))

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

I’m lost…. I can’t keep up anymore. My, what a mess!

Faithful Group B’r for a long time thanks to the relentless, impeccable work and help from Woody et al, but it is getting too hard to keep up with all those updates for updates, patches for patches, and breach after breach.

Windowgeddon is here. (Hopefully not to stay)

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

4 users thanked author for this post.

Charlie, JDeC, HiFlyer, Cybertooth