When one sets Windows Explorer to remember each folder's settings, desktop.ini will be in MANY folders. (do a search on the root of your drive including subfolders and system files/folders)

One work around is to then delete all of them listed in the start menu folders in documents and settings (both for the user and all users).

I would try to NOT use those tweaks in nLite and make the changes via Windows Explorer tools/folder options instead, and see if that problem disappears.

You can also uncheck the show hidden, system files, and see if that doesn't help.

I use english Xp on my first PC and french in seconde.......and I have always same probleme !!

how to fix that ??

Did you do an upgrade as opposed to a fresh install of windows?

However I have a better idea.  You may have "Hide protected operating system files" unchecked in your folder options.  If that is the case it would indicate to me that you accidentally put in a registry hack/patch that you didn't need.  To check/fix open up any folder/explorer window and Tools > Folder Options > View (tab).  Scroll down a little bit (3 or 4 lines) and make sure "Hide protected operating system files" is checked.

Finally (if that's not the case) - Are you removing the Windows File Protection?  Since the desktop.ini is normally a hidden file (which is perfectly normal to be there when you customize some sort of folder setting) it would seem that WFP got a bad crack or patch.  If you delete the desktop.ini files - then they should come back as fully hidden (according to http://forums.techguy.org/windows-nt-20 … here.html).

BTW, This is the order of my Integration:

RyanVM Integrator + Addons
Nlite - due to WMP11 Integration (boogys Method) + Tweaks
DriverPacks + All Latest Packs M2 KTD

Tried Integration Driverpacks alone, still got those desktop.ini.

Generally, this could be tracked down to using a non-English copy of XP with the DriverPacks.
However, this does not mean it will occur with EVERY non-Eng copy... (it hasn't appeared for me in quite a while).

I guess it has to do with different encoding of the winnt.SIF (ANSI/Unicode).