A new variant of "error -1103" problems in Professional Posted November 20, 2018 · Report reply Was this file in OneDrive before it was deleted? When this problem with Files on Demand files first reared its ugly little head, any 'local'* copy of a OneDrive Files on Demand file that was deleted would still cause the -1103 error while it was in the Recycle Bin. I never bothered to investigate too far, I negated the -1103 error by not using Files on Demand, but using a reboot to Linux (most of my systems can native boot to Linux if necessary) to look at the files system it appeared that the deleted files only exists as a reparse point in the Recycle Bin folder to the actual location where the file is stored. Information on this is sparse, but it looks like the code that implements the Files on Demand is under certain circumstances creating invalid data structures in the NTFS MFT which most likely confuse Retrospect. When I've tried scanning NTFS volumes from Linux with Files on Demand enabled that give the -1103 error they always reported an unclean with an unknown error. NTFS volumes with Files on Demand enabled that don't give the -1103 error always reports as clean. * I have yet to find where the local copies of One Drive Files on Demand files are physically stored. Trying to resolve the target of the reparse point that is the OneDrive folder leads me nowhere. The local copies of Files on Demand are not much use as backups when Windows 10 won't boot and you need to perform data recovery from Linux.