Default User's Startup folder Windows 8.1 vs Windows 10

1

Just noticed something as I was playing around with the Startup folder of the Default user in both Windows 8.1 and Windows 10: For some reason, on all of my installs of Windows 10, the Default user's startup folder does not exist where it should be, C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup, whereas in Windows 8.1 it exists.

I've seen on the web that it apparently was replaced with C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp starting in Win7, but I have this path in Win8.1 but not Win10. Win10 goes up to the Programs folder, then Startup doesn't exist.

If I manually create the Startup folder in C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\ and deposit something in it, will the OS run it at start or not ?

Because in this case, I cannot use the Startup folder in ProgramData, because the .BAT file will self-delete after usage, but it needs to be ran on every new user's first logon. By putting it in C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup, it would simply copy over to the user's own Startup folder during the user's profile creation, run, and then delete itself.

If manually creating the startup folder does not work, is there an easy way to do what I need to do ? The only other way I've found would be to start the batch file with an IF statement to search whether the result of the batch file exists or not (which is a registry key) and if so then not run, but that means that everytime the user logs on, the batch file will start, which isn't ideal.

Thanks in advance!

Alex Pilon

Posted 2016-08-10T19:45:31.877

Reputation: 25

IN Windows 10 use C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp – DavidPostill – 2016-08-10T19:59:52.090

@Alex: The default user startup folder still works. I verified it now by creating the Default user Startup folder and placing a script there. – w32sh – 2016-08-10T20:15:43.557

@DavidPostill I specifically wrote that I could NOT use this folder, for very specific reasons (see first before last paragraph). – Alex Pilon – 2016-08-10T21:23:45.643

@w32sh Just tested it on my end, seems to be working fine! Hopefully, MS never fixes that apparent "glitch" :P – Alex Pilon – 2016-08-10T21:24:25.253

No answers