Wonderware Intouch Compatibility Matrix -

Marta’s fingers flew. She added the registry key, restarted the historian service, and watched the data lines spike back to life.

Then, at 3:22 PM, the historian stopped logging.

She applied the fix. Then she exported the InTouch application from the Windows 7 machine—a sprawling, 8,000-tag monstrosity controlling fermenters, cookers, and the new CIP system. She imported it into a virtual machine container she’d spun up on the Windows 11 edge server. The container ran a simulated Windows 7 environment. It was ugly. It was unsupported. But the Compatibility Matrix had a second footnote: “Legacy applications may function within Type 1 hypervisors if network stack isolation is enabled.” wonderware intouch compatibility matrix

She’d heard legends. A former colleague in Houston claimed it had saved his refinery from a $2 million upgrade. A Siemens rep told her it didn’t actually exist—that it was a folk tale, a coping mechanism for a grieving industry.

She scrolled the Matrix. No mention of historian issues. That meant it was either a new problem or an undocumented one. She called an old colleague—Dominic, who now worked at a Wonderware (no, AVEVA, she corrected herself) integrator in Baton Rouge. Marta’s fingers flew

She clicked “Go.”

She opened the Compatibility Matrix again. There was a footnote—tiny, almost invisible—next to InTouch 10.1’s DASMBTCP driver. “When migrating to newer OS kernels post-2020, DAServer heartbeat intervals may desynchronize. Resolution: Increase S heartbeat timeout from 30s to 90s in the ArchestrA System Management Console.” She applied the fix

Marta Vasquez, senior automation engineer at Red Mesa Distilling, knew three things for certain as she walked onto the plant floor at 6:47 AM on a Monday.