Topaz Labs is scrambling to contain a critical bug in its Topaz Video AI application that has wiped entire Windows drives for multiple users. The vulnerability stems from a simple path parsing error—a forward slash instead of a backslash in registry entries—that causes the software to create and later delete workspace folders at the root of system drives when it can't properly resolve project paths.

The Bug Explained

The issue was identified by community member latabox804, who traced the problem to the Windows Registry key HKEY_CURRENT_USER\Software\Topaz Labs LLC\Topaz Video. Within this branch, path entries like defaultProjectDir and defaultProjectDirDefault contain forward slashes ("/") instead of backslashes ("\"). When Topaz parses these malformed paths, it fails to locate the intended project folder and falls back to using the root directory of whatever drive the application is installed on as its workspace. Deleting a project or changing settings then triggers catastrophic deletion at that root level. User sdfgsdgssdgdt363fg described the devastation firsthand after encountering the bug in version 1.6.0: "The program froze, and I discovered that all my files on the C: drive had been deleted. Everything was wiped—200 GB reduced to 18 GB consisting only of Windows system files." The user's system became unbootable, requiring a complete rebuild.

Scope of Damage

This isn't an isolated incident. Multiple users have reported similar experiences. User cole13 lost "half of the data" after receiving a "critical error -2146885629," describing how their games, mods, and all other files vanished. Another user, mgawrisch, experienced the bug when changing working folder settings while clicking to update—half their C: drive disappeared instantly. The pattern is consistent: users who moved project folders from default locations or changed workspace settings triggered the path resolution failure. Topaz's official workaround has been to recommend keeping all files in the default "Topaz Video Projects" directory, but this doesn't address the underlying parsing flaw that makes such relocation dangerous.

Technical Root Cause

The registry investigation revealed systemic issues beyond just the project folder path. User samlake documented multiple affected entries including appDataLocalFolder, appDataRoamingFolder, appDownloadFolder, mostRecentlyUsedProjectDir, and previewFolder—all containing incorrect slash characters. Some entries show double slashes or mixed conventions entirely. A user identified as urix.lookin confirmed finding the problematic forward slash in their own registry after reading latabox804's analysis, validating that this isn't a theoretical vulnerability—it's actively affecting real systems with no warning to users before catastrophic data loss occurs.

Workaround and Missing Fixes

The temporary fix involves manually editing the Registry: navigate to HKEY_CURRENT_USER\Software\Topaz Labs LLC\Topaz Video, locate defaultProjectDir and defaultProjectDirDefault, and replace forward slashes with backslashes in the path "C:\Users\[Username]\Documents/Topaz Video Projects." However, requiring users to manually edit system registries to prevent application-induced data destruction represents a fundamental failure of software quality assurance.

Key Takeaways

  • The bug affects Topaz Video AI 1.6.0 on Windows when project folders are relocated or deleted through the app's UI
  • Root cause is forward slashes in Registry path entries that cause incorrect workspace folder resolution
  • When path parsing fails, the app uses the drive root as a fallback workspace—then deletes it along with user data
  • Manual registry editing can prevent triggering the bug until an official patch is released

The Bottom Line

This is exactly the kind of bug that makes users hesitant to trust creative professional software. A path separator mixup shouldn't be able to nuke a person's entire drive, but here we are. Topaz needs to push an emergency hotfix before more people lose irreplaceable work. If you're running this software right now, either lock down your Registry settings or don't touch the project folder locations until there's an official patch.