Latest build .9916 SetupComplete.cmd not executing
- Thread starter cshirley101675
- Start date
M
My2GirlsDad
Guest
I just had a chance to test the updated version and the updates are being added to the setupcomplete.cmd, thank you for that.
I still have one minor issue, that being the setupcomplete.cmd was being created in the $OEM$\$$\Setup\Scripts folder, but now it's being created in the Windows\Setup\Scripts folder. While this is not a major issue and the install works as it should, having it in the $OEM$\$$\Setup\Scripts folder makes it easier to change if one is testing POSTSetup program changes. I had this same issue on an earlier version and you corrected it on version 2024.3.9831. If you would include this in you next update that would be great.
Nuhi thanks for always helping us Win7 guys out. garlin and clang2 thanks for the shoutout.
I still have one minor issue, that being the setupcomplete.cmd was being created in the $OEM$\$$\Setup\Scripts folder, but now it's being created in the Windows\Setup\Scripts folder. While this is not a major issue and the install works as it should, having it in the $OEM$\$$\Setup\Scripts folder makes it easier to change if one is testing POSTSetup program changes. I had this same issue on an earlier version and you corrected it on version 2024.3.9831. If you would include this in you next update that would be great.
Nuhi thanks for always helping us Win7 guys out. garlin and clang2 thanks for the shoutout.
Clang2
Active Member
- Messages
- 263
- Reaction score
- 91
naff all to do with me.
within the last 2 years nuhi added limited support for Vista because someone asked for it.
windows 7 has a much larger user+fan base so i reckon nuhi will support w7 for another 3 to 5 years at least and while windows 10 and 11 rightfully get all the attention windows 7(and 8.1) issues will hopefully be fixed as and when they arise.
within the last 2 years nuhi added limited support for Vista because someone asked for it.
windows 7 has a much larger user+fan base so i reckon nuhi will support w7 for another 3 to 5 years at least and while windows 10 and 11 rightfully get all the attention windows 7(and 8.1) issues will hopefully be fixed as and when they arise.
Last edited:
M
My2GirlsDad
Guest
Upon further testing I have found another instance where, in my opinion, the setupcomplete.cmd needs to be in the $OEM$\$$\Setup\Scripts folder.
When making an ISO with more than one "version", ie. Home Premium and Professional, the setupcomplete.cmd in the subsequent versions does not include the updates and only includes the POST-Setup items. Another words the updates show up when WU is run. The first version works as expected.
Thanks nuhi
When making an ISO with more than one "version", ie. Home Premium and Professional, the setupcomplete.cmd in the subsequent versions does not include the updates and only includes the POST-Setup items. Another words the updates show up when WU is run. The first version works as expected.
Thanks nuhi
- Messages
- 3,946
- Reaction score
- 1,651
The reasons why it would choose inside the image are:
- editing an isolated image, that is the install.wim taken out of the ISO folder before loading it
- there is already a setupcomplete.cmd in the image, then it just continued there
If your situation does not fit these, please upload the clean image and a preset which demonstrate the problem and share privately.
Thank you.
- editing an isolated image, that is the install.wim taken out of the ISO folder before loading it
- there is already a setupcomplete.cmd in the image, then it just continued there
If your situation does not fit these, please upload the clean image and a preset which demonstrate the problem and share privately.
Thank you.