New
#140
the backup application could not start due to an internal error 0x80070422
the backup application could not start due to an internal error 0x80070422
Just curious if anyone has any idea why Win10 is also trying to include 2 of my Data Drives ( d:+e:) in a system image, it of course means the image is massive, in this case a reported image size of 801 GB ( not mb)
thanks
Okay thanks for the quick reply ............... it makes sense now ......... on this system I have my Library Locations moved to d: and e: to save space on the SSD as it's only 120GB. I guess I will just have to continue using Macrium Free instead.
I posted a thread re my machine not cloning properly from a small SSD to a larger one - but using the clone to boot I got a blue screen (not BSOD) but saying something to the effect that Windows hit a problem and I am sure this was the error code that was quoted.0x8007042
In the other thread Martijn (axe0) suggested a backup being made and then put that backup onto the larger drive. My concern is that I have activated my main AV on the original drive and I don't want to have to go explaining to Kaspersky why I am trying to use the same code if a I did a clean install again on the larger drive. Looking at the possible size of the backup I shall have to use an external spinner and I am just left wondering just what to do.
I've just discovered a serious issue with W10's backup/restore routine that is happening on both x86 and x64 installations, and with public release and fast ring builds.
When an image is restored, any custom photo albums created with the W10 photo app are broken. What you see are just grey tiles and if you try and open them there is no content. The auto generated 'albums' are OK.
I've used the feedback app to report this issue.