I'll look at the script to see if there's any code that changes this. I just checked and there's nothing that could change this time synchronization behavior. As @hoak said, it could be a Windows issue. Do you remember which SD version was used to create your image a year ago? I ask because I've been modifying and removing code that can cause problems over time, and perhaps this might have existed in the past.
@ashish1989 In further research, I discovered that in @Wojciech Keller's original code there was code that disabled time synchronization. The code was as follows: On my Windows 10 IoT Enterprise LTSC 2021 x64 system, the HKLM\SOFTWARE\Policies\Microsoft\W32Time key doesn't exist. And the HKLM\SYSTEM\ControlSet001\Services\W32Time\Parameters key is the one that's attached. Check and modify your registry to see if it works. In our current code, this no longer exists.
I have made a new ISO with slimdown 1.35, and the problem is I can not do a in place upgrade, the setup file is in another folder and when I am trying to run it, it is throwing problems.
I don't know if this is interfering, but rebuild the ISO after removing these lines from the script: lines 2312 through 2327
Make sure the new ISO is the same edition, Pro, Enterprise, etc. Make sure you run it from Admin account, the error you posted is caused by trying to change a service startup type from a local account. If your live system was created with an old version of the script, you should do a clean install, as many core modifications were made since that will cause issues if you try to do in place upgrade.
Did you remove the code indicated in the topic below and redo the ISO? https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/page-46#post-1892569