Windows Mobile 6.5: Cold Boot vs. Warm Reset

Windows Mobile 6.5 managed system restarts through two distinct processes: the warm reset (commonly known as a soft reset) and the cold boot (often referred to as a hard reset). While a warm reset acted like a standard PC restart to clear volatile memory and resolve minor software glitches without losing data, a cold boot re-initialized the hardware and wiped user storage to restore the operating system to its original factory state. Understanding how Windows Mobile 6.5 handled these two operations relies heavily on the operating system’s persistent storage architecture.

The Role of Persistent Memory

Prior to Windows Mobile 5.0, older Pocket PC devices kept user data and the file system in volatile RAM backed by a secondary battery. Windows Mobile 6.5 utilized a persistent storage model where the operating system, installed applications, and user files resided in non-volatile flash ROM (NAND flash). Volatile RAM was strictly reserved for program execution. This architectural standard directly defined the behavior of both warm resets and cold boots.

Warm Reset (Soft Reset)

A warm reset terminated all running processes and restarted the Windows CE kernel without altering non-volatile memory.

System Execution: The operating system flushed pending write operations if possible, shut down active device drivers, and cycled the CPU. The system then reloaded the Windows Mobile 6.5 kernel and core services into execution RAM directly from the persistent storage.
Data Impact: All personal data, installed third-party programs, custom system settings, and registry changes remained intact. Only unsaved application states or active data held exclusively in volatile RAM were lost.
Trigger Mechanism: Users typically triggered a warm reset by pressing a recessed pinhole button on the device chassis using a stylus, or by selecting a software-driven restart option provided by the device manufacturer.

Cold Boot (Hard Reset)

A cold boot was a destructive recovery action designed to completely wipe the device and restore it to the default factory configuration defined by the device manufacturer’s ROM image.

System Execution: During a cold boot, the device bypassed normal boot sequences. The operating system formatted the internal storage partitions holding user data, re-created a clean file system, and reset the Windows Mobile registry to its factory state. It then repopulated necessary default system files from the protected, read-only system ROM partition.
Data Impact: All user data, downloaded applications, SMS messages, contacts, email accounts, and customized configurations were permanently erased. Upon completing the boot process, the device launched the out-of-box setup wizard, requiring the user to re-align the screen, set the time zone, and reconfigure the device.
Trigger Mechanism: Because of its destructive nature, executing a cold boot required deliberate physical intervention. This was usually accomplished via a hardware key combination—such as holding down two specific physical buttons (like Call and End) while pressing the reset pinhole—or by navigating to a secure "Clear Storage" or "Master Reset" utility within the Windows Mobile 6.5 system settings and entering a confirmation PIN.