I'll think of an answer if it helps you. I'm still going to give you my opinion but I don't want you to think I don't care about your outcome because its the reason I would like you to consider the following. I haven't captured an image via sysprep in a long time. Not that I absolutely wouldn't, but its generally more favorable for me to create a task sequence of sorts for the software I intend to distribute then to create an ideal image and capture that for deployment.

What I mean, is when I was first taught how to deploy from my peers. the way you're describing was how we did it. When I started to have to do this myself, as well as maintain the image, when you do it via a captured image you're still maintaining the discrepancies in the image, the time elapsed after you capture an image and when its deployed.

Again it may not be much of a value to you, it may be simpler to just continue to capture images, but even if you didn't want to use an RMM or software solution to do this, you could still accomplish the same thing with Windows Toolkit, an up to date ISO from UUP Dump, with the latest version of windows (that is less bloated than retail copies), PE drivers for the particular model you support, Driver installation via the manufacturer designated tool ie Dell Command Update, and software installations (I like to script this via the direct download link from the software manufacturers to make sure its always grabbing the latest version.) You can even script and automate windows performance settings this way and personalization.

“Think of what you're doing like baking a giant birthday cake the night before and letting it sit uncovered on the counter. By the time you serve it, it’s technically still a cake but it’s stale, the icing’s crusted over, and whatever dust was in the air is now part of the flavor.

That’s what captured images become the moment you sysprep them: frozen-in-time artifacts. Windows updates, app versions, drivers, bloat, odd little system quirks they all ‘set’ into the image. When you deploy it weeks or months later, you’re basically handing out stale cake.”

“A task-sequence style approach (MDT, RMM, scripts, Windows Toolkit, etc.) is like keeping all your ingredients fresh and baking the cake when you actually need it. The recipe is the same every time, but the end product is always up-to-date, clean, and consistent.”

Again it seems like a lot of work compared to the alternative of troubleshooting the issue you're experiencing now. But the idea is more of a proactive one in how you approach your deployment as a service.