There is a way to bypass that limit. You can do a substitute command and set a
drive letter to whatever path you like. Same applies to mapping a network
drive. That's actually one of the more common reasons we see that happen,
although certainly not to the extent you've described.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Neil Standley
Sent: Wednesday, June 1, 2016 3:03 PM
To: [email protected]
Subject: RE: [NTSysADM] RE: Windows 10 upgrade issue
I cannot browse the full path, it's 1600+ folders deep, multiplied by 9
characters in each folder = 14,643 characters in the path, and that doesn't
include the initial path from "C:\Users\User\AppData\Local\Microsoft\Windows
Mail\".
All total, with backslash characters it's 16,341, a tad more than Windows' 260
character limits can handle.
I'm not certain the setuperr log includes the whole path, it may have truncated
because setup encountered the issue and exited.
Neil Standley
Cascadia Infotek
2516 Holgate St
Tacoma, WA 98402
Main #: 253.683.4216
Desk #: 253.683.4226
[email protected]<mailto:[email protected]>
Formerly Net-Venture
[https://owa.nventure.com/img/CascadiaInfotek_Logo_RGB_Web_sm.jpg]<http://www.cascadiainfotek.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Christopher Baio
Sent: Wednesday, June 1, 2016 11:44 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] RE: Windows 10 upgrade issue
What's preventing you from moving the folder if you can browse to the full file
path?
--
Christopher Baio
Desktop Support Technician
CSDNET, Inc
csdnet.net
________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] RE: Windows 10 upgrade issue
Date: Wed, 1 Jun 2016 18:25:41 +0000
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]>
[mailto:[email protected]] On Behalf Of Melvin Backus
Sent: Wednesday, June 1, 2016 10:43 AM
To: [email protected]<mailto:[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
