Enormous number of Microsoft Catalog entries are dated July 13 — tomorrow!

Topic

New Reply

Quick. While it’s still July 12. Take a look at the Microsoft Catalog and see how many entries have a “Last Update” entry of July 13.
[See the full post at: Enormous number of Microsoft Catalog entries are dated July 13 — tomorrow!]

3 users thanked author for this post.

columbia2011, Microfix, Elly

Reply | Quote

Replies

Maybe someone’s set the date reference to a different landmark/timezone…?

1 user thanked author for this post.

Elly

Reply | Quote

Kirsty wrote:

Maybe someone’s set the date reference to a different landmark/timezone…?

Or maybe Microsoft needs to stop calling these “Security and Quality Rollups”

“Security and Poor Quality Rollups” anyone?

1 user thanked author for this post.

HiFlyer

Reply | Quote

Yeah,I wondered if it was a UTC timestamp, but I don’t recall seeing a mass change like that.

Checking again this morning (US time), I see the stamps haven’t changed .. and I have no idea what happened.

Reply | Quote

I think time travel of patches is the most probable cause..

2 users thanked author for this post.

BobbyB, HiFlyer

Reply | Quote

witp wrote:

witp

Back to the Future Marty.

 

1 user thanked author for this post.

BobbyB

Reply | Quote

While I like a good old “Time Travel” theory, I am going to go with “Plausible denial” conspiratorial take.
“What do you mean that patch “Bricked” your Machine on the 12th? it didn’t come out until the 13th”

1 user thanked author for this post.

HiFlyer

Reply | Quote

Happy Friday the 13th.

No matter where you go, there you are.

2 users thanked author for this post.

HiFlyer, abbodi86

Reply | Quote

Given the quality of the patches, Friday 13th seems to be the appropriate date.

Windows 10 Home 22H2, Acer Aspire TC-1660 desktop + LibreOffice, non-techie

3 users thanked author for this post.

Charlie, HiFlyer, BobbyB

Reply | Quote

My thoughts exactly!

Even astrophysicist Carl Sagan when speaking astronomically used Billions, not Trillions.

Reply | Quote

JULY UPDATES

2018-07-11 — KB4338818 (Monthly Rollup) offered this morning.

THE NETWORK DRIVER PROBLEM STILL REMAINS according to MS info

NOT INSTALLED

2018-07-13 — KB4338818 (Monthly Rollup) REMOVED THIS AFTERNOON !!!!!!!!!!!

Something strange is going on — possibly called Microsoft ?????????????????

mbhelwig

2 users thanked author for this post.

Chessie, HiFlyer

Reply | Quote

The old saying, ‘the second mouse gets the cheese’ springs to mind when dealing with Microsoft patches..

Microsoft mousetrap!

Windows - commercial by definition and now function...

3 users thanked author for this post.

Charlie, HiFlyer, WildBill

Reply | Quote

Regarding the issue of the networking bugs:  A support case was opened and the word came back that this primarily impacts those with virtualization/VMware.  If you aren’t running that, you won’t be impacted.  VMware is a virtualization platform.

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

Microfix, HiFlyer, woody, WildBill

Reply | Quote

RE:
“Something strange is going on — possibly called Microsoft ?????????????????”

I’ve called them a few things this week already, none of which are permitted in this forum

1 user thanked author for this post.

HiFlyer

Reply | Quote

“Patches you can trust….”

Interesting… I cannot remember the last time I trusted a Microshaft patch.

2 users thanked author for this post.

HiFlyer, WildBill

Reply | Quote

Running Windows 8.1 & it’s after 4:30 AM Central time. I checked Windows Update via Control Panel & via the PC Settings app under Update and recovery. Anything not Windows Defender, Silverlight & KB3080109 is dated 07/09/18 in the app. In Control Panel, they’re dated 07/10/18. Will check both later today to see if they change to 07/13/18. BTW, I’m on Group A, so I usually don’t download from the Microsoft Catalog. Not looking now… because I trust Woody!

P.S.: I trust Susan the Patch Lady too. What she said…

A support case was opened and the word came back that this primarily impacts those with virtualization/VMware.  If you aren’t running that, you won’t be impacted.  VMware is a virtualization platform.

I’m not running VMware or Hyper-V, I’m on Windows 8.1 Home.

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

1 user thanked author for this post.

HiFlyer

Reply | Quote

Since it’s Friday the 13th you know something will go wrong with these updates.

Reply | Quote

Yeah, and MS will assume they have a good excuse.

Even astrophysicist Carl Sagan when speaking astronomically used Billions, not Trillions.

Reply | Quote

All Tuesday’s patches were re-dated to July 13, except .NET 4.7.2 and Office

never saw such mass date revision before
maybe they heard the complaints abouts dates not matching actual release dates

3 users thanked author for this post.

Microfix, HiFlyer, geekdom

Reply | Quote

Maybe these July 13th patches will install perfectly, in a sort of reverse-Friday-the-13th scenario.  MS patches have worked so poorly every other day.  Maybe these patches are the ones that will install perfectly on this day only.

Then again, maybe someone has already disproved this theory.

Reply | Quote

Huh, I’ve been offered KB4056254 and KB4023057 in addition to the feature update, Flash security update and MSRT. I think they’re annoyed I keep blocking 1803.

Win10 Home, network set to metered, ooooolllddd AMD CPU

Reply | Quote

Windows 7 Group A. As of 10:20 am this morning all of the patches I’m offered in WU (July rollup, .net rollup, msrt) are all still dated July 10th with only the msrt being checked for download & install. I have hidden the .net 4.7.2 update and kb2952664.

1 user thanked author for this post.

HiFlyer

Reply | Quote