Inspiring

Microsoft 2026-02 Security Update (KB5077181) (26100.7840) Crashing Adobe Apps

Forum|Forum|10 days ago
February 20, 2026
2 replies
399 views

Hello Adobe Community,

The latest Microsoft micromalware security update, 2026-02 Security Update (KB5077181) (26100.7840), is once again generating 0xc0000142 for the newest Adobe versions of Premiere Pro, Media Encoder, After Effects and Audition. Even Bridge is affected! Designers and writers report the latest InDesign also does not work.

When attempting to open up Premiere Pro, the Event Viewer generates this information:

Faulting application name: UIFlowService.exe, version: 2.58.163.25188, time stamp: 0xa18b8abc
Faulting module name: MSVCP140.dll, version: 14.13.26020.0, time stamp: 0x5a39fef7
Exception code: 0xc0000005
Fault offset: 0x000000000001b93c
Faulting process id: 0x2508
Faulting application start time: 0x1DCA286DB729A9F
Faulting application path: C:\Program Files (x86)\Power Automate Desktop\UIFlowService.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCP140.dll
Report Id: d520dd69-379c-4bd5-a8f5-c19a9c99b539
Faulting package full name:
Faulting package-relative application ID:

The Open procedure for service "WmiApRpl" in DLL "C:\Windows\system32\wbem\wmiaprpl.dll" failed with error code The device is not ready.. Performance data for this service will not be available.

We do have the latest C++ library installed, but I am referring to a lot of PCs in the organization.

We went through this shlock many times in 2025 and the last quarter of 2024, now its back in 2026, with a vendetta, almost like, its sabotage by very wicked Microsoft engineers. IT is checking into suppressing this Micromalware update. The latest Adobe apps were working great for an entire month, until this treacherous update dropped. Now we have to revert back to the old runtimes. Except that we are not. This time, I am fighting back and with furious rebukes to Micromalware…

Please tell us what we are missing here (for the unteenth time), before I write a full report to the Federal Government of the United States of America. What is Microsoft trying to do with their updates—outdo China, North Korea and Russia hacking America?

FulStak VideditrAuthor

Inspiring

We may have found the overall cause of all of this.

Our IT department injected one of our production machines with Claude to perform computer forensics on Windows 11 Enterprise. To explain the best I can, it is the program/service PAD (Power Automation Desktop) that is the main cause. Because PAD loaded before the Adobe products, it would generate phantoms of references (or misdirect, etc.), preventing Adobe apps from referencing the proper locations, specially making it difficult to access the most up to date in the registry. Here is how Copilot explains it:

This service loads WinAutomation‑based automation runtime assemblies — including C++ components that Adobe also relies on.

Because UIFlowService starts before Adobe, it can load:

Mismatched VC++ runtime versions
Phantom copies of MSVCP modules
Hooked automation interfaces

This precisely matches the Adobe crash logs you reported.

Once PAD was disabled/uninstalled, Adobe apps started loading normal. There appears to be a conflict/flaw between the new Adobe Creative Cloud runtimes and PAD for Windows Enterprise. So IT will be rolling out a removal of this service for the creative department.

I am rather shocked, that when I reported to Microsoft and they ended the report with no actual fix, a PAD conflict was not on the list of possible solutions to check for.

FulStak VideditrAuthor

Inspiring

How do we convert a 26.0.1 Premiere Pro project to a 25.2.3?

We have 2026 new runtime projects that will not open with the 25.2.3, the present working version, until the listed above Microsoft security update can be removed from the system, if it can be.

The same issue with After Effects. As you can see, this malware anti-security update is already causing a cascading effect.

Thank you for any help.