[bphlpt]

First, please forgive me if I have misunderstood how any of this works since I do not use nLite.

@andros - If I understand your question, after using nLite on two different PC's, if you remove "HIDE" in the line in SYSOC.INF, then you see nLITE in "adding / removing components", but if you try to uninstall or remove nLite it doesn't go away and you want to know why and how to get rid of it, do I understand your question? Have you searched in Program Files to verify if the nLite executable is actually there? If the nLite executable is not on the PC, then it is not installed.

@submix8c - I've never used nLite, but from what I've read about it and from reading your answers here, even though nLite is used in building the image that is installed, nLite is not actually installed on the resulting PC, so the nLite entry in "adding / removing components" is just a phantom entry, only visible if the "HIDE" is removed, which is why the "HIDE" was put there in the first place, is that correct? If andros does not want the phantom entry there he should just leave the "HIDE" alone or eliminate the entire line in SYSOC.INF, are those his only options? Is there no other way to eliminate the nLite entry after the fact through the registry or something?

Perhaps someone should contact Ricktendo64 or someone else who might be willing to lend a hand with translation to/from Spanish since that seems to be part of the problem in this thread?

Cheers and Regards

[submix8c]

Nope... the "Components" section of the INI indicates "removed" components. As stated, the nLite.inf only "adds" registry entries and kicks off "nhelper" as a "runonce". I've already done a "test run" of nLite with a similar scenario to ensure I was correct in my "assumptions" (inspecting the "outcome"). I generally remove nothing since IMHO it gains little and only slip updates/drivers and maybe create a User - "KISS" method. In the OP's case they (apparently) used a Dell OEM source (like mine) to:

[Tasks]
Remove Components
Unattended Setup
Integrate Drivers
Tweaks
Create a Bootable ISO
Options

The language is kind of irrelevant. I've already checked with a "translator" to compare. The "run" was done with Spanish as the Language against a Dell Spanish source (apparently based on the OP's comments and the INI).

This post has been edited by submix8c: 28 September 2012 - 08:48 AM

[Ponch]

To sum it up, it's all resulting in a cosmetic problem that is triggered by a deliberate unneeded change and that has no consequence at all since the resulting install is for personal use only. Well, not a big deal I would say.

[Kelsenellenelvian]

Basics of the sysoc file:

It is used mainly during windows setup to tell windows which .inf's to run to install windows components.

The ones with the "Hide" in the entry have those FOR a reason!

Mainly due to the fact the entries are NOT entered to make that component removable!

Or

Removing it can usually cause instabilties or damage.