"Could not open inode XXXXXX through the library..." Windows 10 Sysprep Capture
-
I was messing with the other model of laptop that was now giving me issues. It was dying at random points of the capture. It was actually overheating. I grabbed a different laptop of the same model and it worked like a charm.
So, all of my capture issues so far have seemed to be hardware related.
-
-
@Sebastian-Roth I have been updating all my older images and as part of the process I am removing the windows update files to make the images smaller. This triggered this same error. I tried your wget command to get the new inits but that didn’t solve my issue. I’m on the latest dev-branch as of the time of this post.
-
@kafluke You may have to defragment the drive and/or run chkdsk on it if you’ve deleted a significant amount of data.
-
@Quazz I saw a post by you in another thread and took your advice. I ran all these commands and it’s capturing now:
dism /online /cleanup-image /startcomponentcleanup dism /online /cleanup-image /restorehealth sfc /scannow chkdsk C: /f -
@kafluke I also was experiencing this same issue. I had deleted a bunch of data as well before trying to pull the image (ran disc cleanup wizard). I ran the exact commands you did, and it fixed the issue. Thank you and Quazz for this assistance. This forum really helps in every way with this awesome product.
