New
#11
Nice work Mystere!
I've got a theory about this (I see it a lot at work).
At work, the errors come on individual files during a copy operation.
I do not see any errors during an installation - and don't often go looking to delete the Windows.old folder (we usually only delete it if the system is running short on storage space).
I'll have a deeper look next time I encounter it.
I suspect that there's several possible issues here:
1) that the filename length thing is/isn't being tripped during the temporary copy operations (where Windows uses the free space on the drive before it actually copies it to the new location).
2) that the addition of the Windows.old folder makes the length go over the limit
3) If, at some point, the operation becomes a rename (rather than a copy) operation), then I'd have to suspect that the rename operation doesn't take the length of sub-file name lengths into consideration.
4) That the routine that makes the Windows.old folder is fault/error-tolerant and it's forced to copy everything (despite any rules) because this is a critical process during the installation
As such, I wonder if there are errors listed in the installation log files. It would be good if you could search inside the logs for the filenames that have been seen as being too long.