I recently installed a version of nLite on a computer, and after booting I noticed that a few things went wrong.
Unfortunately, I am my support personnel, so no help there.
The only services that are being started (despite most being set to "automatic") are:
Additionally, I can't run msconfig.
This problem is similar to this question, but I only got this working after much trouble and strife, and quite a bit of luck, so reinstalling won't work. Not to mention the fact that I can start the services at all, attempting to start them gets partway done, then stops. The status in the Services window says "Starting," and stays there.
Is this the same problem? Is there another way around it? Could my nLite commands have caused critical systems to stop functioning?
Well, considering that the point to nLite is to strip Windows down as much as possible, and that if you make a misstep, the installation will be corrupt, then yes, I would say that you configured something, somewhere wrong such that the installation you ended up with was not complete or sufficient enough for a proper install of Windows. What’s more is that you yourself admit to having a lot of problems and strife trying to get it to work, which is an even bigger indication that the installation you produced is no good.
Further, the services were not actually getting “partway done, then [stopping]”. That would imply that they were successfully starting for a bit then getting stuck. What’s more likely is that a part (eg a thread) was crashing (silently) or having trouble locating dependencies and simply not failing immediately. Again this is likely because of too much getting stripped out.
You’re not getting Luna because it needs the Themes
service to be running, which is clearly not the case for the aforementioned reasons. Google Chrome won’t install because it too requires some services to be running which your system is having trouble doing. The same goes for the Installer
service.
The service that you do have running are indeed the bare minimum that is required to have Windows XP run (actually you can forcibly kill the Audio
service without killing Windows). You just stripped out too much.
I’m afraid that your best bet is to reinstall with either a standard install, or at the very least to re-configure nLite, watching carefully what you strip in order to avoid taking out required components.
If you really insist on trying to fix your broken install, it will be a heck of job since you have no way of knowing what files, registry entries, services, etc. are missing. What you could try is to use some programs such as Filemon/Regmon/ProcMon to monitor the system while you try to start a service or run an app to see what items are being accessed to try to figure out what is missing, then try to find a way to add/install the missing items. (Note all the tries.)
User contributions licensed under CC BY-SA 3.0