Neil, I ran across one machine that failed with this error (or close to it). We decided to cut our losses (or at least the time involved) and back up data, do a 'save nothing' upgrade, then reinstall apps and data after the upgrade. That went fine.
Wish I'd heard your diagnosis, as I suspect, knowing what I do about the tendencies of users, that we would have found something similar in the way of deeply nested folders. Seems like there's an easy experiment here. Move the data, upgrade, and put it back. Wish I could try that. If I run across this error again, perhaps I can. Good luck. I'd be interested to hear how this turns out (off-list, if you don't want to share globally). Frank Ress Gas Technology Institute From: [email protected] [mailto:[email protected]] On Behalf Of Neil Standley Sent: Wednesday, June 01, 2016 12:13 PM To: [email protected] Subject: [NTSysADM] Windows 10 upgrade issue I have a client attempting to upgrade 8.1 to 10, but it is failing with the error 0x8007002C - 0x4000D. The installation failed in the second_boot phase with an error during migrate_data operation. The setuperr log seems to indicate the issue is thousands of nested folders under C:\Users\username\AppData\Local\Microsoft\Windows Mail\migbackup\ which creates a path more than 260 characters long and the upgrade is choking on it. 016-05-26 00:21:03, Error SP Error WRITE, 0x000000CE while gathering/applying object: File, C:\Users\username\AppData\Local\Microsoft\Windows Mail\migbackup\migbackup\migbackup\migbackup\migbackup\...... When I copy the whole error message from the log in to Word and do a word count it shows 1627 instances of "migbackup". Has anyone seen or heard of this before? My Technet and Google searches are returning useless results. Thanks, Neil ________________________________ This communication is for the use of the intended recipient only. It may contain information that is privileged and confidential. If you are not the intended recipient of this communication, the disclosure, copying, distribution or use hereof is prohibited. If you have received this communication in error, please advise me by return e-mail or by telephone and then delete it immediately.
