- Jun 30, 2004
- 16,127
- 1,741
- 126
I have a dual-boot Win7/10 configuration that is absolutely stellar and perfect. After tweaking and perfecting every aspect of the hardware, I've cleaned up just about every red-bang and yellow-bang in my event-logs. As we all know, some errors and warnings are benign, some can result from using older hardware and drivers with a new chipset, and some can't be ignored -- or shouldn't be.
System backups are being taken with Macrium, and only in Windows 10. The Win 7 partitions are backed up as unlettered drive volumes, along with the "system Reserved" and Win10 EFI stubs. Perfect restoration is guaranteed.
There are to my estimation six volumes visible to either OS: three with drive letters and three without in either case.
Originally, I just accepted the Windows default for "system protection," and VSS shadow-copies were being taken on everything, but I judged that they shouldn't be. You would only take VSS shadow-copies on drives that are being used by the current OS -- again, either way.
These warning bangs seem to occur not long after boot-time. You would find that an "NTFS" information event would occur after each -- if not each and all. There were six of these Event ID 4's in succession after boot-up. The message is:
"File System Filter 'wcifs' (version . . .time-stamp) failed to attach to volume '\Device\Harddiskvolumeshadowcopy nn'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor."
So I tweaked "System Protection" to discontinue and eliminate VSS copies for OS A within OS B, and vice-versa.
Now, there are only three such errors after boot-time.
All disks are connected to the onboard Intel controller but one. This latter is connected to a PCIE-x1 Marvell controller, and it only contains a single full-disk partition/volume. That volume is equally accessible from either OS. VSS shadow copies are not implemented for that drive -- by either OS.
Other information at "Ten Forums" and MS sites like Tech-Net suggest this is a Windows 10 bug.
Macrium seems to have all the VSS shadow-copies it needs -- if it needs any from the OS. Backups and restores have gone forward without a hitch.
Any more information someone might have about this? Any insights as to what is going on, on whether my choices are good or could be made good or better?
System backups are being taken with Macrium, and only in Windows 10. The Win 7 partitions are backed up as unlettered drive volumes, along with the "system Reserved" and Win10 EFI stubs. Perfect restoration is guaranteed.
There are to my estimation six volumes visible to either OS: three with drive letters and three without in either case.
Originally, I just accepted the Windows default for "system protection," and VSS shadow-copies were being taken on everything, but I judged that they shouldn't be. You would only take VSS shadow-copies on drives that are being used by the current OS -- again, either way.
These warning bangs seem to occur not long after boot-time. You would find that an "NTFS" information event would occur after each -- if not each and all. There were six of these Event ID 4's in succession after boot-up. The message is:
"File System Filter 'wcifs' (version . . .time-stamp) failed to attach to volume '\Device\Harddiskvolumeshadowcopy nn'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor."
So I tweaked "System Protection" to discontinue and eliminate VSS copies for OS A within OS B, and vice-versa.
Now, there are only three such errors after boot-time.
All disks are connected to the onboard Intel controller but one. This latter is connected to a PCIE-x1 Marvell controller, and it only contains a single full-disk partition/volume. That volume is equally accessible from either OS. VSS shadow copies are not implemented for that drive -- by either OS.
Other information at "Ten Forums" and MS sites like Tech-Net suggest this is a Windows 10 bug.
Macrium seems to have all the VSS shadow-copies it needs -- if it needs any from the OS. Backups and restores have gone forward without a hitch.
Any more information someone might have about this? Any insights as to what is going on, on whether my choices are good or could be made good or better?
Facebook
Twitter