Applying a WIM with duplicated file entries
I wanted to cleanup the partition table on my drive, so I grabbed another drive and made a Windows To Go workspace. In that WTG system, I backed up my exising Windows 10 with DISM. Then I cleaned the disk and re-partitioned before I attempt to apply the WIM image back.
Now however I attempt to apply or mount the image, both DISM and ImageX get stuck and quit at file UsersiBugAppDataLocallxssrootfslibxtableslibip6t_HL.so
. Both are reporting "Error 5: Access denied." I know it's a file from Windows Subsystem for Linux.
I set up 7-Zip and opened the WIM file and it seems OK. I navigated to that folder and was surprised to see 2 files with the same name there, only differing by cases. That is, I have libip6t_HL.so
AND libip6t_hl.so
in the same place. I think that's the problem because NTFS doesn't have its case sensitivity support enabled by default (it does have support, though).
So how can I apply the WIM correctly? I am eager to destroy those files (or even the whole WSL setup if required).
windows-10 windows-subsystem-for-linux dism wim imagex
add a comment |
I wanted to cleanup the partition table on my drive, so I grabbed another drive and made a Windows To Go workspace. In that WTG system, I backed up my exising Windows 10 with DISM. Then I cleaned the disk and re-partitioned before I attempt to apply the WIM image back.
Now however I attempt to apply or mount the image, both DISM and ImageX get stuck and quit at file UsersiBugAppDataLocallxssrootfslibxtableslibip6t_HL.so
. Both are reporting "Error 5: Access denied." I know it's a file from Windows Subsystem for Linux.
I set up 7-Zip and opened the WIM file and it seems OK. I navigated to that folder and was surprised to see 2 files with the same name there, only differing by cases. That is, I have libip6t_HL.so
AND libip6t_hl.so
in the same place. I think that's the problem because NTFS doesn't have its case sensitivity support enabled by default (it does have support, though).
So how can I apply the WIM correctly? I am eager to destroy those files (or even the whole WSL setup if required).
windows-10 windows-subsystem-for-linux dism wim imagex
add a comment |
I wanted to cleanup the partition table on my drive, so I grabbed another drive and made a Windows To Go workspace. In that WTG system, I backed up my exising Windows 10 with DISM. Then I cleaned the disk and re-partitioned before I attempt to apply the WIM image back.
Now however I attempt to apply or mount the image, both DISM and ImageX get stuck and quit at file UsersiBugAppDataLocallxssrootfslibxtableslibip6t_HL.so
. Both are reporting "Error 5: Access denied." I know it's a file from Windows Subsystem for Linux.
I set up 7-Zip and opened the WIM file and it seems OK. I navigated to that folder and was surprised to see 2 files with the same name there, only differing by cases. That is, I have libip6t_HL.so
AND libip6t_hl.so
in the same place. I think that's the problem because NTFS doesn't have its case sensitivity support enabled by default (it does have support, though).
So how can I apply the WIM correctly? I am eager to destroy those files (or even the whole WSL setup if required).
windows-10 windows-subsystem-for-linux dism wim imagex
I wanted to cleanup the partition table on my drive, so I grabbed another drive and made a Windows To Go workspace. In that WTG system, I backed up my exising Windows 10 with DISM. Then I cleaned the disk and re-partitioned before I attempt to apply the WIM image back.
Now however I attempt to apply or mount the image, both DISM and ImageX get stuck and quit at file UsersiBugAppDataLocallxssrootfslibxtableslibip6t_HL.so
. Both are reporting "Error 5: Access denied." I know it's a file from Windows Subsystem for Linux.
I set up 7-Zip and opened the WIM file and it seems OK. I navigated to that folder and was surprised to see 2 files with the same name there, only differing by cases. That is, I have libip6t_HL.so
AND libip6t_hl.so
in the same place. I think that's the problem because NTFS doesn't have its case sensitivity support enabled by default (it does have support, though).
So how can I apply the WIM correctly? I am eager to destroy those files (or even the whole WSL setup if required).
windows-10 windows-subsystem-for-linux dism wim imagex
windows-10 windows-subsystem-for-linux dism wim imagex
asked Jul 23 '17 at 8:24
iBugiBug
2,56341839
2,56341839
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Finally restored my Windows 10 installation from backup!!!
I used a Chinese utility called WimTool. In its main UI there's a "Edit Configuration" button. I added UsersiBugAppDataLocallxss
to [ExclusionList]
section, then applied the WIM. As expected, the folder was ignored and no more errors popped up. After restoring Windows 10 setup, simply reinstall WSL.
According to my experience, non-Chinese users should be able to do this without that tool, but ImageX. Microsoft provided a tutorial on creating ImageX configuration file, and in the tutorial they disclosed the Default Exclusion List for ImageX (same for DISM). All you need to do is copy down the default list and add the desired line to it. Then when applying the image, supply /Config yourfile.ini
to ImageX and it'll ignore your specified directories.
add a comment |
FYI...
This is a known problem with imagex in Windows 10 1607. There's a Microsoft KB article on it. The article doesn't say if Windows 10 1703 fixes it.
Microsoft's "solution" is to not install WSL before capturing the image. Your solution of excluding the lxss directory is better :-). Still a Pain In The ASCII to have to reinstall WSL.
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
add a comment |
You can use the wimupdate
in wimlib to remove the WSL, and then you will be able to successfully restore the image.
The specific command is as follows:
cat > update_commands.txt << EOF
delete --recursive /Users/{your_username}/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc
EOF
wimupdate {your_backup}.wim 1 < update_commands.txt
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1233549%2fapplying-a-wim-with-duplicated-file-entries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Finally restored my Windows 10 installation from backup!!!
I used a Chinese utility called WimTool. In its main UI there's a "Edit Configuration" button. I added UsersiBugAppDataLocallxss
to [ExclusionList]
section, then applied the WIM. As expected, the folder was ignored and no more errors popped up. After restoring Windows 10 setup, simply reinstall WSL.
According to my experience, non-Chinese users should be able to do this without that tool, but ImageX. Microsoft provided a tutorial on creating ImageX configuration file, and in the tutorial they disclosed the Default Exclusion List for ImageX (same for DISM). All you need to do is copy down the default list and add the desired line to it. Then when applying the image, supply /Config yourfile.ini
to ImageX and it'll ignore your specified directories.
add a comment |
Finally restored my Windows 10 installation from backup!!!
I used a Chinese utility called WimTool. In its main UI there's a "Edit Configuration" button. I added UsersiBugAppDataLocallxss
to [ExclusionList]
section, then applied the WIM. As expected, the folder was ignored and no more errors popped up. After restoring Windows 10 setup, simply reinstall WSL.
According to my experience, non-Chinese users should be able to do this without that tool, but ImageX. Microsoft provided a tutorial on creating ImageX configuration file, and in the tutorial they disclosed the Default Exclusion List for ImageX (same for DISM). All you need to do is copy down the default list and add the desired line to it. Then when applying the image, supply /Config yourfile.ini
to ImageX and it'll ignore your specified directories.
add a comment |
Finally restored my Windows 10 installation from backup!!!
I used a Chinese utility called WimTool. In its main UI there's a "Edit Configuration" button. I added UsersiBugAppDataLocallxss
to [ExclusionList]
section, then applied the WIM. As expected, the folder was ignored and no more errors popped up. After restoring Windows 10 setup, simply reinstall WSL.
According to my experience, non-Chinese users should be able to do this without that tool, but ImageX. Microsoft provided a tutorial on creating ImageX configuration file, and in the tutorial they disclosed the Default Exclusion List for ImageX (same for DISM). All you need to do is copy down the default list and add the desired line to it. Then when applying the image, supply /Config yourfile.ini
to ImageX and it'll ignore your specified directories.
Finally restored my Windows 10 installation from backup!!!
I used a Chinese utility called WimTool. In its main UI there's a "Edit Configuration" button. I added UsersiBugAppDataLocallxss
to [ExclusionList]
section, then applied the WIM. As expected, the folder was ignored and no more errors popped up. After restoring Windows 10 setup, simply reinstall WSL.
According to my experience, non-Chinese users should be able to do this without that tool, but ImageX. Microsoft provided a tutorial on creating ImageX configuration file, and in the tutorial they disclosed the Default Exclusion List for ImageX (same for DISM). All you need to do is copy down the default list and add the desired line to it. Then when applying the image, supply /Config yourfile.ini
to ImageX and it'll ignore your specified directories.
answered Aug 1 '17 at 4:24
iBugiBug
2,56341839
2,56341839
add a comment |
add a comment |
FYI...
This is a known problem with imagex in Windows 10 1607. There's a Microsoft KB article on it. The article doesn't say if Windows 10 1703 fixes it.
Microsoft's "solution" is to not install WSL before capturing the image. Your solution of excluding the lxss directory is better :-). Still a Pain In The ASCII to have to reinstall WSL.
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
add a comment |
FYI...
This is a known problem with imagex in Windows 10 1607. There's a Microsoft KB article on it. The article doesn't say if Windows 10 1703 fixes it.
Microsoft's "solution" is to not install WSL before capturing the image. Your solution of excluding the lxss directory is better :-). Still a Pain In The ASCII to have to reinstall WSL.
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
add a comment |
FYI...
This is a known problem with imagex in Windows 10 1607. There's a Microsoft KB article on it. The article doesn't say if Windows 10 1703 fixes it.
Microsoft's "solution" is to not install WSL before capturing the image. Your solution of excluding the lxss directory is better :-). Still a Pain In The ASCII to have to reinstall WSL.
FYI...
This is a known problem with imagex in Windows 10 1607. There's a Microsoft KB article on it. The article doesn't say if Windows 10 1703 fixes it.
Microsoft's "solution" is to not install WSL before capturing the image. Your solution of excluding the lxss directory is better :-). Still a Pain In The ASCII to have to reinstall WSL.
answered Aug 11 '17 at 18:19
John Q. PublicJohn Q. Public
111
111
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
add a comment |
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
The problem is, I didn't know the bug before capturing, and all I have is the WIM file after formatting the drive and attempting to restore (and noticed the error).
– iBug
Aug 12 '17 at 3:08
add a comment |
You can use the wimupdate
in wimlib to remove the WSL, and then you will be able to successfully restore the image.
The specific command is as follows:
cat > update_commands.txt << EOF
delete --recursive /Users/{your_username}/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc
EOF
wimupdate {your_backup}.wim 1 < update_commands.txt
add a comment |
You can use the wimupdate
in wimlib to remove the WSL, and then you will be able to successfully restore the image.
The specific command is as follows:
cat > update_commands.txt << EOF
delete --recursive /Users/{your_username}/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc
EOF
wimupdate {your_backup}.wim 1 < update_commands.txt
add a comment |
You can use the wimupdate
in wimlib to remove the WSL, and then you will be able to successfully restore the image.
The specific command is as follows:
cat > update_commands.txt << EOF
delete --recursive /Users/{your_username}/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc
EOF
wimupdate {your_backup}.wim 1 < update_commands.txt
You can use the wimupdate
in wimlib to remove the WSL, and then you will be able to successfully restore the image.
The specific command is as follows:
cat > update_commands.txt << EOF
delete --recursive /Users/{your_username}/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc
EOF
wimupdate {your_backup}.wim 1 < update_commands.txt
answered Jan 28 at 14:34
于国瑞于国瑞
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1233549%2fapplying-a-wim-with-duplicated-file-entries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown