And my minimal test works as is likely expected:
if the symlinks were on E:\ when created, then I reboot to ubuntu and capture with wimlib in block device/ntfs-3g mode, and then restore to a bare NTFS partition on C:\, they're all still pointing to E:\, and thus 'broken'... but in the expected way ...
Search found 3 matches
- Tue Feb 25, 2025 8:52 pm
- Forum: wimlib discussion
- Topic: wimlib incompatibility with dism when some reparse points are present?
- Replies: 4
- Views: 323227
- Tue Feb 25, 2025 8:10 pm
- Forum: wimlib discussion
- Topic: wimlib incompatibility with dism when some reparse points are present?
- Replies: 4
- Views: 323227
Re: wimlib incompatibility with dism when some reparse points are present?
Just did a couple tests, no more error in Dism, and I can successfully boot the system I captured with wimlib.
I think I'm going to retry my minimal test with a changed drive letter and see exactly what behavior I get.
I suppose the downside is that if you apply the image on Windows to a volume ...
I think I'm going to retry my minimal test with a changed drive letter and see exactly what behavior I get.
I suppose the downside is that if you apply the image on Windows to a volume ...
- Thu Feb 20, 2025 8:09 pm
- Forum: wimlib discussion
- Topic: wimlib incompatibility with dism when some reparse points are present?
- Replies: 4
- Views: 323227
wimlib incompatibility with dism when some reparse points are present?
Summary:
I think wimlib has a bug when capturing a symlink with a path starting with \\?\. These seem like valid paths that don't involve the edge cases listed in the wimlib documentation for limitations when capturing from a unix block device (dism doesn't appear to dereference or fix them up ...
I think wimlib has a bug when capturing a symlink with a path starting with \\?\. These seem like valid paths that don't involve the edge cases listed in the wimlib documentation for limitations when capturing from a unix block device (dism doesn't appear to dereference or fix them up ...