I'm not sure if it is the same, but I used to have a customer who had this problem. It was a custom install, but it was caused by Explorer.exe process being killed during start up, resulting in that message. A reboot surely fixed it, or manually running explorer.exe from Task Manager if it is available.