I would love to move it, but since the folder is 1600+ directories deep I cannot simply do that. This system was recently (earlier last week) restored to the factory image and updated, so my assumption is that either Windows update, or the Windows 10 upgrade caused this to occur.
Neil From: [email protected] [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Wednesday, June 1, 2016 10:43 AM To: [email protected] Subject: [NTSysADM] RE: Windows 10 upgrade issue Sounds vaguely like the seemingly endless nested appdata stuff you get if you try to remotely recurse a directory tree. I believe it's created by a link/junction which gets reparsed incorrectly. Oddly enough it doesn't show up if you do the same thing locally. You might try moving the offending folder elsewhere on the drive to see if that's really the culprit or just a false alarm. -- There are 10 kinds of people in the world... those who understand binary and those who don't. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Neil Standley Sent: Wednesday, June 1, 2016 1:13 PM To: [email protected]<mailto:[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
