1
Tweaking.com Support & Help / Re: Registry Backup incomplete under SYSTEM account
« on: September 13, 2015, 02:22:41 pm »
Thanks for the quick update, Shane. Just ran v3.2.1 scheduled under the SYSTEM account and all seems perfect.
Tweaking.com Forums
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Tweaking.com Support & Help / Re: Registry Backup incomplete under SYSTEM account
« on: August 27, 2015, 01:14:48 pm »When using the stand-alone Registry Backup program in Windows 10, I noticed that the 'dos_restore.cmd' file inside the backup folder is completely blank. However, this is not the case when backing up the registry in Windows Vista or 7, I noticed that the 'dos_restore.cmd' files in the Vista, 7 backups are not blank and are full of command line restore instructions.Mine are only empty if the backup ran under the SYSTEM account. Under the current user account there's plenty of instructions for restoring inside the cmd file.
Is the blank file by design or is this a Windows 10 bug?
Thank you.
So no, obviously they're not empty by design.
3
Tweaking.com Support & Help / Re: Registry Backup incomplete under SYSTEM account
« on: August 26, 2015, 02:35:17 am »
Thanks Shane. Log showing file in use errors attached.
The dos_restore.cmd file is empty so not sure why it would be created in case of this type of error.
The dos_restore.cmd file is empty so not sure why it would be created in case of this type of error.
4
Tweaking.com Support & Help / (SOLVED) Registry Backup incomplete under SYSTEM account
« on: August 20, 2015, 04:29:49 am »
On my W10Pro system, if I choose to let the program run scheduled under the SYSTEM account, the user part of the registry backup ends up (almost) empty.
Only when run under the current user account results are as expected.
Before I upgraded the OS from W8.1Pro all was OK. Upgraded the tool from 2.x to 3.1.0 but that didn't help.
Currently running the task as the current user to work around the issue, although that requires login.
As an aside: configuring a task for Windows Server 2003, Windows XP, Windows 2000 is not supported under Windows 10, it seems, if that task is to run under the SYSTEM account. I found that out by editing the task in Task Scheduler and upon selecting the SYSTEM account, getting the message "Running a task under a group user account is supported only on Windows Vista or later. To run a task under a group account, you must upgrade this task to a Windows Vista task."
Only when run under the current user account results are as expected.
Before I upgraded the OS from W8.1Pro all was OK. Upgraded the tool from 2.x to 3.1.0 but that didn't help.
Currently running the task as the current user to work around the issue, although that requires login.
As an aside: configuring a task for Windows Server 2003, Windows XP, Windows 2000 is not supported under Windows 10, it seems, if that task is to run under the SYSTEM account. I found that out by editing the task in Task Scheduler and upon selecting the SYSTEM account, getting the message "Running a task under a group user account is supported only on Windows Vista or later. To run a task under a group account, you must upgrade this task to a Windows Vista task."
Pages: [1]