What Microsoft owes customers, and answers to other 'WannaCry' questions

Most of the hits were on Windows 7 not Xp. I see so many Windows 7 systems that the Windows Update system is broken. We've had lots of topics here on Technibble about it. People also shut down Windows Update in aggravation over the Get Windows 10 nagware/malware that Microsoft shoved down at end users. They turned it off and never knew they could turn it back on.
 
Knowbe4 had an interesting blog post yesterday that might be relevant. According to this post, Microsoft is claiming that no currently known ransomware strain can infect Windows 10, and that the latest creator's update adds a good bit of security which should prevent or limit future ransomware strains. I know we all bash Microsoft pretty regularly, and I'm inclined to be skeptical. However, it's worth keeping an eye on this:

https://blog.knowbe4.com/finally-next-windows-version-10-stops-ransomware-cold
 
Last edited:
  • Like
Reactions: GTP
Most of the hits were on Windows 7 not Xp. I see so many Windows 7 systems that the Windows Update system is broken. We've had lots of topics here on Technibble about it. People also shut down Windows Update in aggravation over the Get Windows 10 nagware/malware that Microsoft shoved down at end users. They turned it off and never knew they could turn it back on.
I think the issue of how often Windows Updates is broken is the biggest issue MS has in regards to what and who they owe. People can often just go about assuming something like that is still working and never think about when they last saw their PC update.
 
It's not tinfoil, I cannot find the tech brief that reports on it. But Windows 7 uses the old XP update, individual patches over time. Windows 10's updates stream in, very much like the image based install. MS updated the entire update cluster and made some sort of bridge... but to understand the bridge Windows 7 needs an update! Which is why it's such a relative pain to get Windows 7 and 8 systems to properly update these days off fresh installs.

As for Windows Update being out of whack, that's what Continuum is for. Patch management is MSP job #1. Heck, even Avast Business FREE AV reports on it. No excuse for updates to be out of date on anything properly managed.
 
It's not tinfoil, I cannot find the tech brief that reports on it. But Windows 7 uses the old XP update, individual patches over time. Windows 10's updates stream in, very much like the image based install. MS updated the entire update cluster and made some sort of bridge... but to understand the bridge Windows 7 needs an update! Which is why it's such a relative pain to get Windows 7 and 8 systems to properly update these days off fresh installs.

As for Windows Update being out of whack, that's what Continuum is for. Patch management is MSP job #1. Heck, even Avast Business FREE AV reports on it. No excuse for updates to be out of date on anything properly managed.
While I haven't used patch management outside of a company setting I know that even they break as they tend to see rely on the Windows Update system to actually install the updates which if broken your patch management still means nothing.
 
It still reports the break at least, but it also has built in remediation for the known errors of windows update version deficiencies.

I've just put continuum on fresh Win7 and watched it work as a result. But, you don't need it if you've kept Win7 current. The people with busted updates are the ones that didn't reboot in a timely matter for automatic updates, or disabled it for months on end because muh computer.

My personal favorite are the tools out there whining that Windows Update "broke" their computer. I haven't had an update brick a machine since Windows 2000. Bad updates happen, but thanks to my west coast living, generally they are pulled before they get to me. The few that got through were fixed without my input anyway.

The boxes that broke were almost all viral... infection damage is always a thing.
 
It's not tinfoil, I cannot find the tech brief that reports on it. But Windows 7 uses the old XP update, individual patches over time. Windows 10's updates stream in, very much like the image based install. MS updated the entire update cluster and made some sort of bridge... but to understand the bridge Windows 7 needs an update! Which is why it's such a relative pain to get Windows 7 and 8 systems to properly update these days off fresh installs.

As for Windows Update being out of whack, that's what Continuum is for. Patch management is MSP job #1. Heck, even Avast Business FREE AV reports on it. No excuse for updates to be out of date on anything properly managed.
Sounds like you are referring to the fact that Windows 7 updates are now in concurrent rollups. I am referring to the fact that many systems cannot do updates. A fresh install of Windows 7 will often NOT update and you have to manually find a series of patches to get WU to work again. This started about the time Windows 10 hit the scene and many feel it is a deliberate "poisoning of the well" to push end users over to Windows 10. The patches that I have seen are NOT directly related to Windows update. (It's not a new copy of BITS for example). I've NEVER seen any reference that the windows update system had changed for Windows 7. Really would like to see that link.
 
Microsoft is claiming that no currently known ransomware strain can infect Windows 10
I believe that is in reference to the as yet unreleased Windows 10 S. That version only runs apps from the Microsoft Store, in the same way that an iPhone only runs approved apps from Apple's App Store.
 
Sounds like you are referring to the fact that Windows 7 updates are now in concurrent rollups. I am referring to the fact that many systems cannot do updates. A fresh install of Windows 7 will often NOT update and you have to manually find a series of patches to get WU to work again. This started about the time Windows 10 hit the scene and many feel it is a deliberate "poisoning of the well" to push end users over to Windows 10. The patches that I have seen are NOT directly related to Windows update. (It's not a new copy of BITS for example). I've NEVER seen any reference that the windows update system had changed for Windows 7. Really would like to see that link.

I would love to provide it, but I cannot seem to locate it. It was a tech brief on windows update changes. Windows 10 uses a very different update engine, and MS was busy trying to adapt a bucket of stuff to a better model. In theory, Win7 from scratch to current is easier today because all you need to do is apply the latest update rollup, and the most recent windows update client. In practice... not so easy. The same holds true for Win8 now, it's not just 7 that is busted on a fresh install.

Win10 is actually busted on a fresh install too! If you go back to the originally released build, it's a bugger to get going. The "fix" however is the much easier process of getting the update tool and manually updating to the most recent build.

XP did this too... we just had the ability to get service packs back then and slip stream them into media so things would work after the fact. But, even with SP3 integrated disks I do not want to go back to the days of having to manually update IE to get things going again. 2000 had a similar collection of insanity, involving the .net framework to get updates rolling.

In short, it's a thing. It's not "easy" to install a new OS. That is, unless you're on an image based installation OS, which is what Windows 10 is. The new windows update on Windows 10 exists because of these problems. Where the tin foil can come out is where MS is basically telling people if you want this junk fixed you need Win 10. Because honestly, Win7 is done, support is out in Jan 2020. Win10 has an updated driver model that adds support for all sorts of things Win7 just cannot do.

MS really should just release SP2 for Win7 so we can all make updated disks for fresh installs that just work, that would help. But they're too busy calling service packs "releases" now, to get server owners to pay for an R2, and pushing update rollups just means more work for us IT people. On one hand... yay for job security on the other... WTF are they smoking?

But, I get a ton less stressed when I see Win10 sitting there... official media is a google search for Windows 10 Media Creation tool, and updates are just the same, thumb drive and install with minimal issues. I do NOT miss the old days.

Trolling the internet looking for a clean ISO for 2000, XP, Vista, or 7?

How about different disks for each distribution channel?

Nope... I'll take Win10.
 
I am referring to the fact that many systems cannot do updates. A fresh install of Windows 7 will often NOT update and you have to manually find a series of patches to get WU to work again. This started about the time Windows 10 hit the scene and many feel it is a deliberate "poisoning of the well" to push end users over to Windows 10.

I've noticed this, and it's been driving me bananas. Interesting.
 
I've noticed this, and it's been driving me bananas. Interesting.

It was a problem with the July 2015 (I think) update. Some systems just hate it and WSUS Offline doesn't help. We just saved the manual patches labeled Patch 1, Patch 2, etc on our shop-share and run those on systems that need it. Once you figure out the workaround it's not bad.

We generally use images for N&P's though and since they're all updated once a month, it's only an issue for us on the rare system that needs to be installed from DVD or on systems that are in the shop for something else.
 
Back
Top