Backups failing after Win 10 upgrade to 1803

I upgraded to Win 10 1803 on 30th Apr.. and yesterday was first time my backup run. 2 of my 3 backups ran fine - the third failed. saying "Failed to back up file or folder 'E:\'. It may be blocked by another application." which is strange, my E drive hold nothing active, it just holds personal files (e.g. pictures, old save games, word docs etc.. i.e. no active progs running from it) and nothing was open.. and I was doing it from a clean boot.

It SHOULD backup about 138GB, but when it fails it gives option to ignore/ignore all - so to try and skip an individual issue I said ignore.. and it now "succeeded" .. but only backed up 11GB.. so clearly its not done its job.

I deleted the whole backup (i.e. in Acronis and the historical backup files) and started from scratch - but had same issue.

So I downloaded the MVP log viewer and the bit of interest seems to be

Which is interesting - as I had specified it should backup all the files in the drive EXCEPT the onedrive folder. and even if it just skips that.. it should still backup the 138GB.. and not the 11GB it has done. So its skipped other stuff I cant see from the log?

I would go on to say how BAD Acronis is in handling this..in terms of how badly the prompts and alerts around the error are handled.. but this post long enough already.. so if anyone can give me a pointer to whats going wrong here and how to fix - would appreciate it.

Thanks in advance

P.S. I am WIn 10 prof 1803.. and I am Acronis TI 2018 11530, also OneDrive is not running (I only run it when I want it to sync).

Yoji, there have been a number of reports of issues with backing up OneDrive folder contents after the Windows 10 Spring 1803 update - some of this can be associated with the Files on Demand option for OneDrive which leaves zero length symbolic links on the drive.

I would recommend opening a Support Case directly with Acronis Support to register this problem and have them investigate it further, along with those cases raised by other users in the same area.

One other suggestion, try reselecting both the Source and Destination data for this backup in the ATI GUI - these Windows Upgrades can result in changes to the drive UID which can cause other issues.

Yoji, sorry I did miss the point that you had recreated the task, however the log message clearly shows involvement with OneDrive as below:

E0004000C: Failed to back up file or folder 'E:\'. It may be blocked by another application.
The file is read-only. (0x4000C)
function = "OpenFileW",
path = "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\OneDrive",

I have only seen this blocked issue with OneDrive folders regardless of it being excluded in your backup. It may be an issue with Microsoft VSS used to create snapshot data given the reference to the ShadowCopy path - if so, try running the free Acronis VSS Doctor tool (link in my signature) to see what that reports?

Which seems suggest a problem with C drive.. but E/ is green - but is mentioned (none of my other drives even mentioned).. I don't really understand what this is telling me.. but would you recommend I just press the "fix issues"? and would you think/hope it might fix my issue?

Considering the whole thing we talking about in this thread - your confidence in quality of Acronis software is maybe a tad misplaced.. ;)

But I took the plunge - and pressed the fix button.. all it said it was going to fix was to increase the C Drive Max VSs to 21GB.. no change to E drive settings.. so I was not hopeful.

it went through OK - I rebooted - rechecked and it VSS doctor said all was OK. So I deleted the problematic backup again - rebooted - and started again from scratch... but as feared - I got the same problem.

So I moved my OneDrive folder off of the E drive.. and then redid the backup and it all went through fine, backing up the expected/normal 138GB

So I have a workaround to my problem - but I go back to being very unhappy with the quality of Acronis software.. check through my prev posts.. I have had WAY to many problems .. it seems that EVERY new version of Acronis.. or every ver update to Win 10 seems to bring problems, and I don't think I am a sophisticated user.. I just want the basics (i.e. totally reliable backup to/from a NAS), I shudder to think what it would be like if I tried use the more esoteric features.

Anyway - Thanks for your help.. may be they will fix in an future update (but they really need get ahead of these problems.. and fix BEFORE win 10 updates released to production).

Yoji, glad that you have got a work-around by moving your OneDrive folder but Acronis will only consider investigating this type of problem if users like yourself are willing to raise a Support Case and provide them with the diagnostic information from an Acronis System Report to work with.

This particular problem looks to be triggered by the latest Windows 10 #1803 update in conjunction with OneDrive but it is not impacting all users of ATI 2018. Is this a problem that Acronis can or should fix, or is it one that Microsoft needs to fix - only the developers would be able to tell us?

I removed the offending folder/file from the Acronis backup; copied the offending folder to another hard drive; deleted the offending folder/file from the original location; restarted my PC; copied the offending folder/file back to the original location from the hard drive I had copied it to; added the file/folder back to Acronis backup; and the backup now runs without error.

As for OneDrive, I have reported it to Tech Support in a case file. They are looking into it. If you run an image backup of your drive, OneDrive will be included.

Philip, welcome to these User Forums and thank you for sharing your experience with seeing the same problem and that you have opened a Support Case - please let us know as you get any feedback from support.

When you say "offending folder/file" - I presume you do mean its the OneDrive folder?

But your comment - that putting it back did not cause the issue to reappear, is interesting. Just for clarity, when you put it back, you did make it the OneDrive folder again? so when you put it back it was a working OneDrive folder, synching with OneDrive cloud etc?

That would be interesting - though not sure I can be bothered to go through hassle of checking it in my case. Having moved my oneDrive folder and its 103GB contents.. I am inclined to leave it be now ;)

Hopefully my post helped you get to solution and we didn't have to solve it independently.

Please try reselecting your Source and Destination data for your backup - the error suggests that the drive or partition unique identifier has changed as a result of your Windows Update (CheckVolumeDeviceIdMatch). This has been seen by other users / reported in these forums.

You look to have fallen foul of the other issue - where MS changes the drive ID when they do the update..Steve eludes to this when he says (see above)

One other suggestion, try reselecting both the Source and Destination data for this backup in the ATI GUI - these Windows Upgrades can result in changes to the drive UID which can cause other issues

I think I had a related issue as part of my Win 10 update to 1803 (I presume that your version - 1809 not out yet!!!) when what shoul dhave been my hidden system recovery drive became visible all of a sudden (so I had to rehide it again). But that a Win 10 issue - not Acronis (though you would hope they handle it better, or even code to cover such things if they know it can happen).

I have found that rescheduling appears to solve the problem for local backups. I have not yet found a solution for the problem with cloud backups. I am one-eyed at the moment (cataract operation) so I am a bit off centre. Decided to de-schedule my cloud backup and create a new one. Before doing so I also did a disk cleanup deleting the old Windows installation. (I have slow internet upload so will not know if this combination of actions solved the problem until tomorrow.

Ian

Update: the backup failed to complete, so there is something very wrong introduced by the latest Windows 10 build. Will now definitely contact tech support. I wonder why it seems to be more prevalent with backups to the cloud?

I'm seeing this same issue, and I believe I've managed to narrow it down (in my instance). I am also on W10Pro 1803 and this is a OneDrive subfolder.

Anyway, I checked attributes on affected vs non-affected files, and I am seeing the 'hidden' (as in attrib.exe can't set/unset it) Attribute "L" indicating a Reparse Point as being the culprit. As I said, you can't remove this Attribute with attrib.exe, but I found a way around by copying the affected files to and back from a FAT32 volume which does not support Reparse Points and strips the Attribute. After this operation my backup completes successfully.

@IanL-S.. but check my situation (I started this thread).. My OneDrive folder WAS excluded from the backup - but the backup still failed. So there some extra complexity in there. To get my backup to work - I had to move my OneDrive folder off of the drive. Though interestingly - another contributor was convinced it was an attribute of that folder causing the problem.. and I could have moved it back if I had cleared that problem attribute by copying to a FAT32 drive first - and then copying back.

FYI - 1803 has a fair share of problems, some that were known last month and prevented the release then, some that are creeping up now. Those of us who move to the bleeding edge updates as soon as they come out, are prone to have issues as we're the real guinea pigs. Once the dust has settled on the update, we should see some fixes from Microsoft and Acronis to deal with the new changes.

For me, the problem was also connected to reparsepoint information in the onedrive files.

Using powershell, you can quickly check whether your OneDrive files have reparsepoint information by running

`Get-ChildItem`

in the OneDrive folder.

I personally believe that with the 1803 update, at least for some of us, OneDrive was updated and the option "Files on Demand" was automatically activated. Further I believe that for this feature to work, OneDrive added this reparsepoint information to the files and that it not deleted when turning the feature off (I'm not saying that it should be).

For some reason this reparsepoint info breaks Acronis and given that reparsepoints are a rather old NTFS feature, I think that this may actually be a bug in Acronis that has only been "triggered" by the recent Windows/OneDrive update. Regardless, I'm sure that the devs will soon find a workaround.

Getting rid of the reparsepoint info indeed allowed me to backup again. Rather than copying everything to FAT32 and back, I used this script, which removes the reparsepoint info from all files recursively.

USE AT YOUR OWN RISK, I HAVE NO CLUE WHAT THE LONG TERM EFFECTS MAY BE!

Thanks for this information. May I suggest you pass this on to Acronis Technical Support (if you have not already done so you will need to create a case - there are several cases already and you could a cross-reference to the one I created - 03348785. The last I have heard back is that the problem is being experience by many users and has been escalated. No hint of there being a solution.

I am experiencing problems trying to backup after upgrade to Windows build 1803. Previously scheduled backups will not run. If I attempt to change the destination by clicking on "Browse", ATI will freeze.

I have tried deleting the existing backup profile and recreating a new one. Same result, ATI will freeze when attempting to locate a location.

I have an old, complete system backup, and can restore selected files but if I attempt to change this profile destination, same result.

I have uninstalled ATI 2016 and reinstalled and the same problem exists. FRUSTRATING

If you have already uninstalled / reinstalled ATI 2016 for this issue, then the only other options would be to perform a totally 'clean' install of the product, or else to try an upgrade to a later version of ATI such as a 30-day trial copy of ATI 2018.

When you say that ATI 'freezes' when trying to change or set the Destination location - is this for all tasks, new and old, or is it for certain specific tasks? How long have you waited for the freeze to clear?

I have used ATI 2017, 2018 and the 2019 Beta products on Windows 10 Spring Creators Update #1803 all without any similar issues.

Note: to perform a clean install, do the following:

Uninstall ATI 2016 normally via the Windows Control Panel.

Download the Acronis Cleanup tool (link in my signature) and run this as Administrator.Note: this will also remove Acronis Disk Director if installed plus will remove all backup tasks & task history etc.

Restart the computer to complete the cleanup action.

Download the final full installer program for ATI 2016 from your Acronis account and install this from an Administrator account (to ensure correct / required authority and privileges are given).

FIrst to answer your questions, ATI 2016 would freeze anytime I attempted to Change Destination - "Browse" on both a new or old profile.

As you suggested I uninstalled ATI 2016 from the Control Panel and rebooted. Then I ran the cleanup IAW https://kb.acronis.com/content/48668 . I then reinstalled, and after logging into my account, all appears to be working now.

Program also found my previous backups on my external hard drive. It allowed me to reconfigure each of my two previous profiles (Full System, Selected folders).

Kristin, are you including OneDrive in your source list of folders to be backed up? If so, then check that you do not have 'Files on Demand' enabled for OneDrive because this will cause Acronis to have problems due to the way that the links to the files in the OneDrive Cloud are created.

With ATI 2019 the problem is not solved for cloud backups (one drive folder is excluded by default) but is apparently fixed for local backups (I could be mistaken about this - I only use OneDrive for business which did not exhibit this problem). I you use cloud backup there is an option to backup OneDrive remotely; ATI Cloud server directly updates from the Microsoft OneDrive server which eliminates the problem.

I have various Acronis backups. They are all local source files backed up to local destinations. The first error I noticed (yesterday just after updating the Acronis program) referenced my local OneDrive folder.

Before anything further, today I deleted all of my tib files.

After further looking, I noticed that two other backups (unrelated to OneDrive) referenced three specific files in the same type of error message. Two of the files were recently added image files (I was still able to open them in Photoshop). I renamed the files but Acronis found and "rejected" them again. I chose ignore and the backup completed successfully. Strangely, after opening these files, I was not able to move them, even after restarting the computer (however, I was able to delete them).

The third file that was referenced was a Quicken backup file. I deleted the file and that backup completed successfully. Attached screenshot.

I don't know enough about Acronis to know if the image files and the Quicken backup file may have been damaged by some type of conflict? At this time, all of my backups seem to be functioning.

Kristin, without seeing the logs for the various backup tasks to see whether the same Quicken backup file features in each case, we can only go with the information from your image.

When I have seen this type of error previously, this can be caused by either a security application such as antivirus blocking access or else because the application which created / owns the file has locked it, i.e. this has been seen for QuickBooks database files where the recommendation is to use the applications own backup tools to capture such files.

The screen image shows that the error is happening after Acronis has tried to include the Quicken backup file in the snapshot data captured by the Microsoft VSS (Volume Shadow copy Service), rather than the original file (C:\2XXX.Documents.Program\2XXX.Quicken\BACKUP\CHRYSALIS PRIME-2019-05-05.PM04.03.QDF-backup).

If Quicken provide their own backup tools, then this should be used and if including the backup file created by those tools, you should ensure that the file is not still locked by the tools or make a copy of the file into another location.