Since AVEVA acquired Wonderware, the compatibility landscape has shifted dramatically. With the sunset of Windows 7 and the rise of subscription-based license models, knowing exactly which Operating System (OS), SQL version, DAServer, and Virtualization platform works with your specific InTouch version is no longer optional—it is mandatory for system stability.
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. Then she exported the InTouch application from the
InTouch uses Microsoft SQL Server for tag management and alarm logging. It was ugly
She stopped at the main HMI terminal, its screen flickering with the familiar teal-and-gray interface she’d known for fifteen years. “Old friend,” she muttered, tapping the touchscreen. “Today we find out if you speak their language.”
“The one where engineers annotate their own findings. Look at the entry for InTouch 10.1 SP3 with Historian 9.0 on NTFS volumes larger than 2TB. There’s a handwritten note—I swear it’s handwritten in the PDF—that says: ‘SQLite timestamp mismatch. Set registry key: HLM\Software\Wonderware\Historian\UseSystemTime=1.’ ”