ZeldasLegend

Unfortunately the problem has re-ocurred again regarding the disappearing tools in Windows 10 x64 on my desktop. It could be a coincidence but it crashed around the time my computer was accessing a Blu-Ray via AnyDVD HD and PowerDVD 14. I uploaded the generated log files as well a few hours ago using the form on the log collection page.

Quick update that as of 01:27 am CT on 08/24 I still haven't had the pool disappearance issue re-occur since KB 3081441 cumulative update was installed on 08/21. Two updates were installed but unfortunately they are cumulative updates and for the second one the updates actually installed should be one of the fixes dates on or after August 13th in the KB page: 1) Security Update for Microsoft Windows (KB 3081444) installed on 08/21 => a single new Internet Explorer update was included in this cumulative update and thus is unlikely to be the culprit. 2) Update for Microsoft Windows (KB 3081441) installed on 08/20 (auto-installed during the reboot after the final pool disappearance/crash) => the latest Windows cumulative update which supercedes the previous cumulative update (KB3081440 released on I believe August 12th which should have already installed on my PC the previous week as part of the mandatory updates - it is not listed in my installed updates presumably since KB 3081441 replaced/superceded it) Attached (it didn't publish in a readable manner) is an extract from KB 3081441 of all of the Windows 10 64-bit updates that were published on or after August 1st, 2015 (i.e., I stripped out those prior to those date since I'm definitely no more than 1 week behind on Windows 10 updates) KB 3081441 x64 updates published after 08-01-2015.doc

Additional information for the pool disappearing issue I'm having with Windows 10. Ever since my last reboot which triggered the installation of new Windows 10 updates (I'm on the slow cycle for updates which are still forced updates) the issue hasn't re-ocurred. Granted it has only been about a day but this is a good sign compared to my experience the last couple of weeks so I thought I'd mention it in case the Windows 10 updates does end up resolving my issue.

Unfortunately each time I've rebooted the collection of logs is automatically stopped in the app. The most recent occurrence had the pool fail within 30 minutes. I found the following error message in Event Viewer: "Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\,0x80000000,0x00000003,...). hr = 0x80070001, Incorrect function. . Operation: Processing PreFinalCommitSnapshots Context: Execution Context: System Provider" In this specific occurrence the time was 8/20 @ 5:56:41 pm CT. The event source was "VSS", the Event ID was "12289", the task category was none, and the event level was "Error". After this error occurred the pool was gone again (I haven't yet rebooted again due to other ongoing backup tasks that are a higher priority). Less than a minute later there is a single additional event for the source "VSS" which was at time 5:57:36 pm CT. The Event ID, task category, and event level were the same as the previous event. The event details are nearly identical except the second error was ShadowCopy2 rather than ShadowCopy1. "Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\,0x80000000,0x00000003,...). hr = 0x80070001, Incorrect function. . Operation: Processing PreFinalCommitSnapshots Context: Execution Context: System Provider" There are three warnings/errors in the 15 minutes prior to the first event listed above and both of these events are for the source "Kernel-EventTracing". The first is a warning and the second event is an error. The first event (warning) which occurred at 5:56:12 (event ID 4 with task category of "logging") is: "The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes." The second event (error) which occurred at 5:56:12 (event ID 3 with task category of "session") is: "Session "ReadyBoot" stopped due to the following error: 0xC0000188" The third event is an error for source CAPI2 which occurred at 5:56:31 (event ID 513 with task category of "none") is: " Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object. Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol. System Error: Access is denied. . " I suspect this information is not of much use without the more detailed log files but unfortunately for this occurrence this is all that I have available. ~John

In case this is the right forum topic to comment on for possible Windows 10 bugs (not to troubleshoot them but simply to note them), I have encountered an issue where my exiting drive pool disappears after having been booted into my Windows 10 Pro desktop for around a day. Rebooting restores the pool but then it takes several hours to be fully synchronized/duplicated again. But each of the last three times the issue re-occurs and the pool is unavailable until I reboot again. The drives associated with the pool are no longer visible within the app as either part of a pool nor are they listed in the non-pooled section even though the drives are still available as normal NTFS partitions for non-pool use. Similarly, the drive letter and virtual partition for the pool also disappear once this problem occurs at which the pool is no longer accessible both inside and outside of the app until after restarting my PC. Note that restarting the app doesn't help with this particular issue, hence rebooting to restore the pool.