This is a fairly common gotcha with Apache/Uniform Server on Windows, and it’s usually not caching so much as name-based virtual host configuration order.
A few things to check carefully:
Ensure NameVirtualHost / default vhost behavior
In Apache 2.4 (which Uniform Server uses), Apache serves the first matching virtual host as the default. If one of your <VirtualHost *:80> blocks is missing a unique ServerName (or both are using localhost), Apache can’t reliably decide which one to serve, so it falls back inconsistently after restarts.
Each vhost must have a unique ServerName (and optional ServerAlias)
Example:
<VirtualHost *:80> ServerName project1.local DocumentRoot "C:/UniServerZ/www/project1" </VirtualHost> <VirtualHost *:80> ServerName project2.local DocumentRoot "C:/UniServerZ/www/project2" </VirtualHost>
Then map both in your hosts file:
127.0.0.1 project1.local 127.0.0.1 project2.local
Avoid using plain localhost for multiple sites
localhost should ideally point to one default site only. Using localhost/project1 and localhost/project2 relies on directory routing, not virtual hosts, which can conflict once vhosts are enabled.
Check that httpd-vhosts.conf is included only once
Duplicate includes or mixed configs can cause Apache to load vhosts in a different order on restart.
Restart Apache cleanly (not just reload)
Stop Apache completely from UniController, wait a few seconds, then start it again. Windows file locks can sometimes make partial restarts misleading.
In short, this behavior almost always comes down to duplicate or missing ServerName entries and Apache picking a different “default” vhost each time. Once each site has its own domain name and matching host entry, the flipping should stop entirely.
This is a fairly common gotcha with Apache/Uniform Server on Windows, and it’s usually not caching so much as name-based virtual host configuration order. A few things to check carefully: Ensure NameVirtualHost / default vhost behavior In Apache 2.4 (which Uniform Server uses), Apache serves the first matching virtual host as the default. If one of your <VirtualHost *:80> blocks is missing a unique ServerName (or both are using localhost), Apache can’t reliably decide which one to serve, so it falls back inconsistently after restarts. Each vhost must have a unique ServerName (and optional ServerAlias) Example: <VirtualHost *:80> ServerName project1.local DocumentRoot "C:/UniServerZ/www/project1" </VirtualHost> <VirtualHost *:80> ServerName project2.local DocumentRoot "C:/UniServerZ/www/project2" </VirtualHost> Then map both in your hosts file: 127.0.0.1 project1.local 127.0.0.1 project2.local Avoid using plain localhost for multiple sites localhost should ideally point to one default site only. Using localhost/project1 and localhost/project2 relies on directory routing, not virtual hosts, which can conflict once vhosts are enabled. Check that httpd-vhosts.conf is included only once Duplicate includes or mixed configs can cause Apache to load vhosts in a different order on restart. Restart Apache cleanly (not just reload) Stop Apache completely from UniController, wait a few seconds, then start it again. Windows file locks can sometimes make partial restarts misleading. In short, this behavior almost always comes down to duplicate or missing ServerName entries and Apache picking a different “default” vhost each time. Once each site has its own domain name and matching host entry, the flipping should stop entirely.