Hello!

I have one really anoying folder %AppData% in my c drive. I'm using runoonceex method in my unattended win xp cd during t-13 setup stage (with "rundll32.exe iernonce.dll,RunOnceExProcess"). After computer reboots, on my c drive there's **** folder %appdata%. I can't delete it with batch, because %appdata% is variable, and my batch deletes whole "C:\Documents and Settings\Admin\Application Data" folder.

Please help anyone.

Ive never heard of anything like this before but it may have something to do with the distributions folders located at $Oem$, $1, $$ etc look at the folder and see which ones you have and then again it could be a folder created through an application!!

%AppData% is where programs store your settings etc. Why would you try to delete something, that is as important as this?

from the sounds of it there is a folder on his HDD

entitled %appdata%

(eg. c:\%appdata%\)

MasterJ you may wanna confirm this.

you may have to hard code the path into the batch to get it deleted though

eg

rmdir c:\%appdir%\

try it out see if it works (i don't recommend doing this on a live machine though, use a test machine)

What about

RD /S/Q C:\^%APPDATA^%

Also if you have a folder by that name, it is due to an error on your part. You would be better off trying to find the cause of the folder creation rather than the fix.

Windows creates that folder because I install soft during t-13 windows installation stage (during setup, not on the first boot).

Windows creates the environment variables such as %APPDATA% before T13, therefore there must still be an error either with something you are doing or with the application which is creating the invalid folder.

Explanation:

• APPDATA=C:\Documents and Settings\%USERNAME%\Application Data
  HOMEDRIVE=C:
  

Therefore the folder is incorrectly being created as %HOMEDRIVE%%APPDATA% i.e C:\C:\Documents and Settings\%USERNAME%\Application Data

Anyhow, did you try the code I gave you to remove it?

<Edit>

It is tested and working on my XP and 2K machines

</Edit>

Edited June 5, 200521 yr by Yzöwl

Sounds like an application is trying to install before the environment variable and physical folder is created. Therefore it simply makes its own and it badly assumes that it should be on your C hard disk.