[Bug/Design Flaw] Stop Polluting System Root with adobeTemp – Violation of Windows Standards

Adobe must stop the automatic creation of the C:\adobeTemp directory at the system root level. This implementation is non-compliant and demonstrates poor design for several reasons:

1. Violation of Windows Filesystem Hierarchy According to Microsoft’s "Certified for Windows" application specifications, temporary session data must be stored within %TEMP% or %LOCALAPPDATA%. Creating folders directly in C:\ is defined as "Namespace Pollution". Modern software should respect the host OS environment rather than treating the root directory as a private dumping ground.

2. Inconsistent and Non-Standard Naming The folder uses lower camelCase (adobeTemp), which is completely alien to the Windows system convention of PascalCase (e.g., Program Files). This suggests a lack of platform-specific optimization in cross-platform components (likely CEP or CCXProcess), where a web-developer's naming habit has bypassed OS-level standards.

3. Failure of Lifecycle Cleanup In most cases, this folder remains empty and persists long after Adobe processes have terminated. It creates unnecessary "digital clutter" that requires manual intervention. If the software creates a directory, it must be responsible for its deletion upon exit.

Required Actions:

• Relocate: Redirect all such data to %LOCALAPPDATA%\Adobe\Temp.

• Standardize: If a root presence is mandatory, at least follow the OS naming convention (e.g., AdobeTemp).

• Cleanup: Ensure the directory is reliably removed when the process terminates.

Adobe should lead by example in software craftsmanship. It is time to address this long-standing disregard for operating system standards.