Windows 10 October 2018 Update rollout now paused

sunberg · 03 Nov 2018

Interesting, I've tried it via Task Scheduler and it didn't work.

muchomurka · 03 Nov 2018

Josey Wales said:

Just backed mine up without any problem-It is FUD

Registry key/hive export IS NOT EQUIVALENT TO registry backup.

- it does not include registry permissions
- it cannot include HKLM\SAM & HKLM\SECURITY hives
- it cannot be fully merged/imported if effective permissions on some keys are Read Only.

Josey Wales · 03 Nov 2018

muchomurka said:

Registry key/hive export IS NOT EQUIVALENT TO registry backup.

- it does not include registry permissions
- it cannot include HKLM\SAM & HKLM\SECURITY hives
- it cannot be fully merged/imported if effective permissions on some keys are Read Only.

Yea right and this issue was in 1803 and 1809..

muchomurka · 03 Nov 2018

Josey Wales said:

Yea right and this issue was in 1803 and 1809..

I am afraid this issue/behaviour started in Windows NT 3.1, 25 years ago. NT Registry is stored in database files, not all parts are fully accessible to users. To back it up (copy db & log files), either databases must be closed (not so easy) or Shadow Copy service must be used.

magilla · 03 Nov 2018

just received patch to new Macrium Reflect 7.2.3825

Josey Wales · 03 Nov 2018

magilla said:

just received patch to new Macrium Reflect 7.2.3825

I got that yesterday morning Magilla.

Josey Wales · 03 Nov 2018

muchomurka said:

I am afraid this issue/behaviour started in Windows NT 3.1, 25 years ago. NT Registry is stored in database files, not all parts are fully accessible to users. To back it up (copy db & log files), either databases must be closed (not so easy) or Shadow Copy service must be used.

So then with 1809 this is a non issue.

magilla · 03 Nov 2018

Josey Wales said:

I got that yesterday morning Magilla.

Just used it today, took yesterday off—shame on me.

magilla · 03 Nov 2018

muchomurka said:

I am afraid this issue/behaviour started in Windows NT 3.1, 25 years ago. NT Registry is stored in database files, not all parts are fully accessible to users. To back it up (copy db & log files), either databases must be closed (not so easy) or Shadow Copy service must be used.

I used to be able to backup registry in 7. Guess I haven’t done so in a long while. Used to be backed up when new installs were made. And we were admonished to back up registry before we made changes to it, but now it looks like backup is not reliable???

Bree · 03 Nov 2018

Josey Wales said:

No the reported issue is FUD, they were saying it existed in 1803 as well..BS.

This bug exists. The scheduled RegIdleBack task runs and shows the result 0x0 in Task Scheduler indicating success. However, nothing has been written to c:\Windows\System32\Config\Regback folder. This task worked correctly in 1709, but has not worked since 1803.

@dalchina and I have been studying this bug for the past month or so. This bug exists on every machine I have tested, be they x86 or x64 versions of 1803. Here's my report of the test results....

... after leaving it idle for about ten minutes the task now shows a Last Run Time of 7th Oct 2018 at 22:31 and a Last Run Result of (0x0). However the files in RegBack are still zero length and dated 19th July. Basically, it appears this task doesn't do the work it is supposed to do.

Windows 10 crashed after update and is now unbootable Solved - Page 3 - Windows 10 Forums