Skip to content
MSP Processes: How AI Is Changing Patch Management episode artwork

Oct 1, 2026 25 min

MSP Processes: How AI Is Changing Patch Management

from SMB Community Podcast: Business Advice for Small MSP Owners Hosted by MSP Radio

The episode scrutinized the operational impact of accelerated patch velocity, largely attributed to AI-driven vulnerability discovery. Microsoft’s patch release cadence has intensified, as evidenced by the increase from 200 patches in June to 900 patches in September. Despite this uptick, panelists noted that patch delivery is now consolidated—vulnerabilities are addressed through a single cumulative update per cycle rather than via hundreds of discrete patches. This structural change reduces exposure to widespread outages, but risk must still be evaluated based on deployment timing and organizational context. Delaying patch deployment by at least one week post-release was advocated as a harm-reduction strategy. The rationale is that “dead body Wednesday”—the day following Patch Tuesday—commonly reveals unforeseen operational disruptions. Forum monitoring and the identification of industry-specific tolerances are recommended, supported by the observation that most incidents arise from edge cases or latent infrastructure flaws exposed by reboot cycles rather than patch malfunction itself. The role of Microsoft in acknowledging and remediating issues was discussed, with a particular emphasis on the lag between incident emergence and vendor acknowledgment. A secondary focus addressed the expanded risk surface beyond Windows, emphasizing IoT, networking, and edge devices. The lack of standardized, automated patching for non-Windows assets, such as security cameras, printers, and other IoT endpoints, multiplies the challenge for practitioners. Neither firmware nor update methodologies are unified, necessitating manual intervention and physical connectivity in many cases. The episode further touched on IT governance concerns, particularly around excessive permissioning, data management, and the tendency for access requests to escalate rather than contract over time, exacerbating organizational risk. For MSPs and IT service providers, key implications center on risk-managed operations. Patch deployment processes should be routinely assessed and customized based on client risk profiles, infrastructure complexity, and historic pain points. Increased vulnerability discovery via AI necessitates enhanced organizational discipline around both patch timing and post-patch monitoring. Security governance—especially regarding permissions scopes, data segmentation, and the extensibility of third-party integrations—was underscored as an operational priority. Comprehensive asset management and organizational awareness of fragmented patch ecosystems, especially in IoT and edge contexts, will be essential for maintaining resilience and accountability. What should I do differently now that AI is throwing us so many patches? Show Rundown & Banter: Amy is joined by longtime Microsoft MVP Susan Bradley, the “Patchaholic,” to discuss Microsoft updates, patching, and what IT professionals need to watch. Question of the Week: How should MSPs change their patching strategy in the age of AI? Microsoft’s updated guidance calls for short quality-update deferrals and faster installation deadlines. https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/references/policies-quality-updates Tales from the Field: When reimaged machines started failing — Susan shares a story involving Dell machines and unexpected failures. Links mentioned in this episode: Question of the Week - Microsoft: Windows Autopatch quality update policies (deferral and deadline guidance) https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/references/policies-quality-updates - Microsoft Mechanics: Deploy Windows updates to counter AI-discovered threats https://techcommunity.microsoft.com/blog/microsoftmechanicsblog/deploy-windows-updates-to-counter-ai-discovered-threats/4534505 Resources - AskWoody, Susan Bradley's newsletter https://www.askwoody.com/ - Third Tier, Amy Babinchak's patching series https://www.thirdtier.net/?s=patch ← swap in Amy's exact link About the SMB Community Podcast: Weekly business advice for small MSP owners from Amy Babinchak and James Kernan of the Small Biz Thoughts community — MSP sales, MSP pricing and agreements, hiring and leading an MSP team, MSP operations, selling your MSP, and AI for small MSPs. Produced by MSP Radio. More for MSP owners at smallbizthoughts.com. SMB Community Podcast is supported by our partners: Oveka Supporting the IT services community through insights, analysis, and transparency.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

MSP Processes: How AI Is Changing Patch Management

0:00 25:30
of matches

Transcript Auto-generated, may contain errors

It may be fall, but winter is coming. BetMGM Casino is putting a spin on the iconic television show Game of Thrones. You can now play the Game of Thrones casino game at BetMGM Casino. Forge your path to the throne with dragon fire and over 4,000 ways to win and more. Journey through Westeros and discover casino excitement like you've never seen before. Download the BetMGM Casino app and check out the Game of Thrones casino game. Will you be next to take the Iron Throne? BetMGM and GameSense remind you to play responsibly. 19 plus to wager. Ontario only. Please play responsibly.

If you have questions or concerns about your gambling or someone close to you, please contact Connects Ontario at 1-866-531-2600 to speak to an advisor free of charge. BetMGM operates pursuant to an operating agreement with iGaming Ontario. This is the SMB Community Podcast, the longest-running MSP-focused podcast in the industry. I'm James Kernan. My background is IT sales, marketing, and leadership, and most recently, M&A Advisory Services. And I'm Amy Babinchak. I help MSPs run stronger, more profitable firms from a tech-first perspective. Here, you'll find practical insights for MSPs and IT service providers. Powered by Small Biz Thoughts.

Today, I'm joined by my longtime friend and fellow Microsoft MVP, Susan Bradley. Susan Bradley is a lot known to many of us as the patchaholic because she just can't get over obsessing over Microsoft's patch routines and what they might be doing to your network. Susan spent a lot of years helping IT professionals, and she does it from the frame of being a forensic accountant and an internal IT person. She is not an MSP like most of us. And I think a lot of people don't realize that because they see you in all the same forums as we are all in.

But Susan, I go way back in the MVP community. I even remember the day that I met you. I met you first at an SMB Nation conference, and there was a bunch of cool kids over by a pool table, and they were clearly the cool kids in the group. And so I started asking around. I'm like, who are those people? They're like, oh, those are Microsoft MVPs. And I'm like, oh, really? I wonder how I become one of those. And I remember you as the, we got you in. See, we had this, we're going to change the world one MVP at a time. And you were doing a lot of ISA. Firewall service. Firewall stuff. And it was like, okay, you know.

And at that time, they had so many people as small business server MVPs, the marketing department kind of went, okay, we can't anymore. And we went, wait, we can slide her in over there as an ISA MVP in the firewall. And then we'll slide her in over here. So we got you in the back door to get you into the main door. And then I was in with the cool kids. And so it was awesome. And I'm going to give a little story, just an off the wall story. I still remember the day you and I were down in Los Angeles. I think we were doing some community event down there.

We're in the hotel room coming back from the event and the guy who was one of the lead product managers and vice presidents, whatever, in charge of small business server is there because I think his daughter was having a wedding at the time. So he's coming in and you could see it was this hilarious thing because at the time you had long hair. It was this hilarious thing because you could literally see him look at you and kind of like, wait, I know this person. Why do I know this person? Because you were like fish out of water kind of thing. And it was like I said, he then snapped on and went, oh, yeah, I know you. So it was the funniest thing of seeing that guy from Microsoft, you know, go, wait, where have I seen this woman before? Why do I know her? And it's not because my daughter is getting married. So I still remember that scene, you know. Yeah, I felt like I should have an invitation to the wedding.

I thought you were going to tell the story of the time when I unplugged the server in the middle of the presentation because it was driving me crazy. That was a true moment. As you can tell, we've had lots of history in the past and including a lot of patching history in the past. And I know you and I have always been a little bit, not at odds, but sometimes different philosophies. Now you, unless you've changed, have always been a put it on automatic, let it rip. Not always, but toward the end of my MSP for sure. Let it roll. Because the number of problems that we had was very, very minimal.

This brings us to the question that we have today. And the question is, what should I do differently now that AI is throwing so many patches at us? And I'm going to break that down between Windows and everything else. So let's focus first on the Windows world. And for me, my philosophy, I haven't changed my patching. What is my patching process? Number one, wait at least a week. Why wait at least a week? Because literally you can see, you can count the days going, patches come out, the main patch comes out on the second Tuesday of the month.

I then call it Dead Body Wednesday. That's the day after patching when everybody who lets automatic machines go, reboots the machines, comes into the office Wednesday morning and goes, wait a sec, I can't do this. I can't print. I can't fill in the blank. And those questions start bubbling up in the forums. Hey, I can't do this. Hey, have you seen this? And it's not until at least Friday night, possibly Monday morning, that Microsoft starts officially acknowledging that, yes, there's a problem. Because sometimes there's patching things that aren't patching related. Sometimes, especially in the MSP world.

And I've literally had this myself where I haven't rebooted something. And this is a non-Microsoft thing, mind you, but haven't rebooted something in a while. And I go to reboot it and the rebooting itself exposes an underlying problem that wasn't patching related. It's just because it rebooted because of patching, it bubbled up. The other day, Hyper-V, I had a PG&E problem where they zapped electricity on me. And when I reconnected things, I didn't properly reconnect an external backup drive. Hyper-V and external backup drives are not happy when you don't connect things properly. And they pause when you don't connect things properly. And the Patch Tuesday process exposed that, hey, it wasn't a happy camper and it didn't have a drive in the proper place. And Wednesday morning, fortunately, it was not a critical machine. It was one of my secondary backup machines. But there's a case where initially I thought, oh, it's a Patch Tuesday problem.

It wasn't a patch juicy problem. It was a stupid Susan problem who didn't connect something right, and the rebooting process just exposed it. So, you know, we sometimes go, oh, it's always patching. It's not always patching. It's not always patching. A lot of times it's old computers, home built or hacked up devices. Whenever I see patching issues, there's a lot of edge cases involved. Most of the time, we don't have a big, widespread, huge outage.

Part of that's because Microsoft changed the way they roll out patches too. They don't roll out the patch to the entire world at the same time. So that meant for me, my clients don't all, every machine in my clients does not get the patch all at the same time. So that worry of, oh my God, what if every client I support goes all down at the same time? Kind of went away. So in June, Microsoft released 200 patches. In July, they released 400 patches. In August, they released 600 patches. In September, they released 900 patches. Okay, I'm gonna argue with you. They patched vulnerabilities, but it's still one patch.

So we're still testing one update. Fortunately, we're not back in the Windows 7 era where we would have had 600, 700 individual updates. We have one. We have one, but you've got all of those vulnerabilities that they're finding now because of AI. That's true. So AI is changing how Microsoft finds vulnerabilities. But I'd argue that you as the MSP still has the same process you should be going through. Patch due as it comes around, you need to have certain machines that you have, testing machines. And let me roll back and say, you also need to determine your risk factor in your businesses. Look back if you're...

historical patch pain. If there's an industry, if you have a client who never, ever has side effects, put those on sooner than versus later. If you have an industry, some client that has massive issues with printing, they have an old printer, they have something, see if you can work around that. See if you can find a long-term solution. In the meantime, you wait. You pause those things for at least a week. You wait for Microsoft to identify issues. And then the other thing is you don't overreact. The main thing I'm seeing right now that AI is having issues with or causing issues is they're making us overreact.

time after time, I will see somebody come out to the forum and say, AI has said this patch causes that. And I'm like, no, it didn't. That's a month ago. We've already fixed that. Or like this recent batch.

Domain machines are rebooting and they're not connecting to the network. It occurred in a small slice. You had to have credential hardening on. You had to have a misconfiguration. By the time we got down to what actually created the problem, all of us in a domain environment were pulling the patch off and saying, hold on, don't put it. And you got down to going, wait a sec. It only occurred this corner edge thing over here. It was not widespread. But if you read the write-up, which was partially created by AI, it was...

You know, every network is going to be impacted. You know, we're all burning down, you know. So it's like, wait a sec, don't overreact. Now, conversely, where I do want you to make changes in your patching because of AI is look at everything else. Look at your firewall. Look at your edge. Look at your VPN. Look at the stuff that you don't have automatic processes to roll out patches. Because that's where AI is going. They're going after the low-hanging fruit. I mean, we haven't changed. They still go after the low-hanging fruit. It's still about the low-hanging fruit. And now they can go into AI search engines and go, how can I better hit Active Directory? How can I better hit Microsoft 365? Do you have multi-factor on those credentials from Microsoft 365? Do you have...

OAuth authorization for administrator only so that users in your organization can't automatically pull in a third-party app and pull it into Microsoft 365. You better make it slightly harder for those apps to be approved. Yes, it's a pain. I'm Dave Sobel, Dean of IT Service Provider University, and I want to let you know about a new class we're offering with instructor Lori Hartke. Lori has run ByteWise since 2008 and still works in it every day. She teaches this from what she lived, not from a framework she read. This is the part most owners will recognize immediately.

It seems that in our industry, everyone measures, focuses on how much revenue one has, and that is how we measure the success of a business. And revenue alone doesn't equal success. A big part of what we're going to work on in this class is making sure that all of the hard work is actually building a profitable business that rewards you as the business owner. Lori's class, Building a Better MSP, starts in October and runs weekly starting Tuesday, October 13th at 1 p.m. Eastern. Register today at itspu.com.

You know, but to your point about AI can attack everything, right? So I just finished writing a whole six-part series on how you should change your patching. And a little bit of it is Windows, but a lot of it is those security cameras, those doorbells, those printers. Remember that some years ago about MGM Casino getting hacked through the thermometer in their fishbowl? That was like a super edge case, but that's going to become common because AI's got all the same security tools that we do and it can act as...

fastest, I mean, it's super fast. It'll find a way through networks and tell you how to hack things. To me, this is where all the patching needs to go, right? And the bummer is that very little of it's automated because unlike Windows and the whole Windows ecosystem, you've got a single patching mechanism. The rest of the IoT world never settled on a single patching.

And so it's all over the place. Some are firmware, some are updates. Most of them are firmware, actually, and there are pain in the neck. Sometimes you have to have like a cable. I have a lovely scanner behind me that in order to get the firmware on that, it doesn't always go over the wire. You have to do that USB connection because that's the only way you consistently get that update down. Yeah. So anything that's connected to your network is now a target. Before, it was a really difficult target. AI makes it a much simpler target.

And then the other thing I'm going to argue, too, is that, again, don't overreact to some of these news stories. Some of what AI is pointing out and Copilot was the same way. It's not that you have vulnerabilities or issues in your network. It's just because you haven't realized you had the permissions set wrong. You know, that thing can get into the payroll section because you didn't set permissions to that location. MSPs are terrible with permissions. We've been terrible at managing data always. Right. The whole idea of.

taking permissions away almost doesn't exist in MSPs because the requests always come in. I need permissions for this. I need you to give permissions to so-and-so for that. Everyone, full access. Yeah, it's never, I need them not to have access to this. I need them not to have, that request almost never comes in. It's always additive. And so an employee there, the longer they're there, the more permissions they have. And also the other problem is, you know, back to the data management is a huge thing. In the server era, we dumped everything into a single folder. And if you came from small business server, it was everything's under company folder. Yep.

Well, you had to give people permissions to that and you could do NTFS and do segmented stuff and all of that. But it really doesn't work in the AI era. It kind of didn't work with cloud because it slows things down to be in one big, huge folder. But permissions wise, it really doesn't work in the AI era. You've got to do data management. So patching of IoT and data management, I think, is where MSPs have to go for the future. That's where their value, where they can still add value.

There was a recent issue that initially we were like, oh, it's a Microsoft. Again, we always love to blame Microsoft. Oh, it's a Microsoft problem. Oh, it's a Microsoft problem. Well, it started out where, and I'll have to look back at the actual KB that introduced this new change. It's been a few months ago. But there was a patch that came out and it had to do with SID hardening, security identification hardening in a network. And all of a sudden,

And we'd see it predominantly in the small business area, not so much in the big enterprises, where somebody would come in and complain that, hey, all of a sudden, because of this patch, they can't see folders on the network. Pull off the patch, everything's OK. So I was like, hmm, OK. So Microsoft had come out with some, you know, about again, about a week later, they come out with, you know, known issues and they come out with some fixes and things like that. And it still wasn't fixing it. OK, it's like, hmm, what's wrong with this? And it's amazing to me of people out in the field, out in the community that will sit there.

and diagnose things and come up and actually identify what root cause is. More so than Microsoft. It's amazing to me. I love people with odd hobbies. So they determined what was going on was these machines that they had purchased through a manufacturer with four letters, starts with a D, through their refurbished store. Again, starts with a D, four letters, refurbished store.

They were selling machines that had duplicate SIDs because they were re-imaging the boxes after they came back in, after they came off of lease. And they weren't doing the, you know, what are they? And I'm pulling a blank here. There's a process where you basically strip out the SID and you give it a new SID. And they were not properly doing that process. So they were shipping them out. And as we are apt to do in small businesses, when the Windows 10s were retiring and we're getting ready to put out the Windows 11, we were buying these things off the refurb store. And just a couple of people were buying duplicates at the same time. So they ended up having exactly the same SIDS. So of course, what did they do in the network? The network was doing what it was supposed to do. It was saying, hey, I won't talk to you because you've got the same SIDS as this guy over here. I'll let one guy in. I won't let the other guy in.

Microsoft sometimes will do this, and it annoys me to no end, is they will gate their solutions behind opening up a support ticket. And if you're an MSP, you know that dealing with Microsoft support is... not the nicest in the world. It's kind of dealing with like dealing with Xfinity support, same kind of like frustration level. Yes. And it annoyed me to no end that you had to call in to get this fix. So I did my, I had a person in the forum and I said, do me a favor. I said, I'm going to, I know the trick. So, and here's a tip for you guys who've never done this before. If there is a security patch and you know, it's causing a issue.

And the root cause is the patch. Call into Microsoft. There is a $500 support call fee if you do not have a support case. You know, I know some of you guys are gold partners, stuff like that. You have support cases. But if you're a smaller partner and you don't have the support cases, go ahead and call in. It's a $400 fee.

you can then ask the manager and have them refund the case. So I did that on behalf of a person in the forum because I was not experiencing the issue, but we wanted to get to the root cause and get to the solution. So I did that, come to find out it was a registry key that they didn't want to publish because they don't want you to have duplicate SIDs. But the, you know, the workaround, quote unquote, is to reimage that machine or use a third party new SID tool that isn't supported by Microsoft. So it's like, this is a machine already installed, already having, you know.

And you don't want to reinstall that thing. We're not big enterprises. Most small businesses, if you're like me, you know, Joe's machine over there is unique to Joe. And it's got different applications than Jane's. So I'm not going to reimage and, you know, pave it down because, you know, she's got her cat pictures on the desktop. And, you know, it's like, no, no, no, no. It's been in the field for six months already. I don't want to reimage that thing. So we got the registry key off. They went and they were happy. But it's like, Microsoft, come on, you know, I get what you're doing here. Yeah.

don't make it hard when it's not this MSP's fault. And these were typically machines bought by MSPs for their small businesses because Windows 10 was expiring and they needed to get Windows 11 out. Well, hey everybody, that's our podcast for this week. I do want to tell you about Susan's newsletter. She has an excellent newsletter called Ask Woody. Ask Woody has been around for a long time. She bought it from Woody and kept the name. A really eclectic bunch of articles and I love it. Give us a little short spiel of what they can expect in the newsletter, Susan. They always expect me. I'm always in every newsletter. And sometimes it's like, it's...

I always have patching issues and then I have non-patching issues. In this last week, it was my experience with migrating to my Apple phone and how many third-party or how many of the... authentication apps came over well and how many I had to go, oops, that didn't work. Yeah, it's always a mixed bag. But you've got a certain set of, you always have the, what's that section called where they have the free apps that one does such an analysis on. It's pretty cool. We have free apps through Windows. We have people that talk about AI and legal issues. So we're bringing in kind of the legality of technology. We have a law professor who brings in a little bit more than you think. We always try to have actionable items.

We have some tools that you can add to Windows or new things that Microsoft is doing. A lot of people are not too thrilled about AI in Windows, so we always like to give you, like, here's how to turn it on and here's how to turn it off. If you want insider knowledge, this is not your newsletter. This is like, I use Windows for day-to-day use. I use it for work. I use it for, you know, I'm using the released versions. I'm not on the insider. I will keep you one step ahead of the feature releases and say, no, no, no, no. You know, don't install it just yet. We're going to wait and see what issues bubble up. So that's the newsletter. If that's your genre, that's our kind of, that's our lane. All right. That's over at Ask Woody. And you guys will have the URL for that in the show notes, of course. And there's also in the show notes, the URL for my...

new patching service series today that I wrote, and it's over at thirdtier.net. Thank you for listening and or watching. Remember, Dave breaks down the IT news of the day on his show, The Business of Tech, which drops at 5 p.m. Eastern, Mondays through Fridays, with bonus content on the weekends. Watching this on YouTube? Be sure to like and subscribe so you always know you've got our latest episode. We'd love to hear from you, so feel free to use the contact form on the SMB Community Podcast webpage. That's smbcommunitypodcast.com. Or leave your comments on our YouTube episode page.

Produced by Picture This Video. Part of the MSP Radio Network.

Frequently asked questions

How long is this episode of SMB Community Podcast: Business Advice for Small MSP Owners?

This episode is 25 minutes long.

When was this SMB Community Podcast: Business Advice for Small MSP Owners episode published?

This episode was published on October 1, 2026.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this SMB Community Podcast: Business Advice for Small MSP Owners episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.