Move Windows 7 to another drive on dual boot machine
I have a dual boot Windows 7 and Ubuntu 14.04 machine both using a 500 Gig SSD. I want to increase the space available to Windows 7 by adding another SSD. Since there seem to be some stories about Windows updates nuking other partitions on the drive it occupies (https://forum.level1techs.com/t/solved-windows10-anniversary-nuked-my-linux-partition-table/110271 , https://www.partitionwizard.com/partitionmanager/partition-disappears-in-win-10-anniversary-update.html , https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-update-messes-with-linux-partition/f3584285-72b7-4f4e-8e7b-5a8b0eadbb72), I thought it might be a better idea to move Windows 7 to its own SSD, separating the two OSs onto their own drives.
I copied my Windows 7 partition to the new SSD using GParted, but when I run "update-grub" from linux to add the new copy of Windows to the GRUB boot menu, it doesn't find the new copy, only the old one. It makes no difference whether the new SSD Windows partition is mounted or not.
What additional steps have I missed here? I only have a vague understanding of how a computer boots up.
Also, is this approach even the best one? If Windows 7 actually doesn't pose any risk to Linux (it's given me no problems for a couple of years), then simply using the new drive as a D: drive for Windows (and some additional space for Linux) would probably be a better idea.
EDIT: I've added a few links to stories of Windows 10 corrupting partition tables to back-up my rationale for moving Windows to its own drive. However, if Windows 7 poses no risk, please feel free to tell me my approach is unnecessary.
dual-boot grub2 partitioning windows-7 ssd
|
show 1 more comment
I have a dual boot Windows 7 and Ubuntu 14.04 machine both using a 500 Gig SSD. I want to increase the space available to Windows 7 by adding another SSD. Since there seem to be some stories about Windows updates nuking other partitions on the drive it occupies (https://forum.level1techs.com/t/solved-windows10-anniversary-nuked-my-linux-partition-table/110271 , https://www.partitionwizard.com/partitionmanager/partition-disappears-in-win-10-anniversary-update.html , https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-update-messes-with-linux-partition/f3584285-72b7-4f4e-8e7b-5a8b0eadbb72), I thought it might be a better idea to move Windows 7 to its own SSD, separating the two OSs onto their own drives.
I copied my Windows 7 partition to the new SSD using GParted, but when I run "update-grub" from linux to add the new copy of Windows to the GRUB boot menu, it doesn't find the new copy, only the old one. It makes no difference whether the new SSD Windows partition is mounted or not.
What additional steps have I missed here? I only have a vague understanding of how a computer boots up.
Also, is this approach even the best one? If Windows 7 actually doesn't pose any risk to Linux (it's given me no problems for a couple of years), then simply using the new drive as a D: drive for Windows (and some additional space for Linux) would probably be a better idea.
EDIT: I've added a few links to stories of Windows 10 corrupting partition tables to back-up my rationale for moving Windows to its own drive. However, if Windows 7 poses no risk, please feel free to tell me my approach is unnecessary.
dual-boot grub2 partitioning windows-7 ssd
A simple copy to another drive will not create another operating OS. Simple copies will copy all of the files, but the copy will not set up the boot configuration so the 'copy' will not be seen as a working OS. The best way to do this is to do a new Windows 7 install on the new SSD and then copy over the files needed for your current setup (programs, documents, pics, etc). There will be some additional work to set up your desktop (prog. shortcuts).
– Craig
Feb 3 at 4:20
If you want to add the full new SSD to Windows, don't do anything! Just add it to the system and create a new drive letter under Windows and then move Windows Data over to that new drive. (off-topic here, so leaving a comment instead of an answer)
– Fabby
Feb 3 at 8:55
@Craig Although that would work, it seems a shame to go to all the effort of doing a reinstall just to obtain a bootable installation. Surely there is a more direct way of making a clone bootable?
– PhilipC
Feb 3 at 20:27
@Fabby This is very easy to do, but I'm exploring the possibility of moving all of Windows to its own drive because of some reports of Windows corrupting partition tables during updates. Microsoft themselves recommend "other operating systems" go on separate drives (answers.microsoft.com/en-us/windows/forum/…) However, if there is no risk of Windows corrupting Linux, I will just add the drive as a data drive and not move Windows. Is this actually a risk with Windows 7?
– PhilipC
Feb 3 at 20:32
Windows corrupting other OSes will happen regardless of whether it has its own boot drive or not. That's why we have boot-repair
– Fabby
Feb 3 at 20:59
|
show 1 more comment
I have a dual boot Windows 7 and Ubuntu 14.04 machine both using a 500 Gig SSD. I want to increase the space available to Windows 7 by adding another SSD. Since there seem to be some stories about Windows updates nuking other partitions on the drive it occupies (https://forum.level1techs.com/t/solved-windows10-anniversary-nuked-my-linux-partition-table/110271 , https://www.partitionwizard.com/partitionmanager/partition-disappears-in-win-10-anniversary-update.html , https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-update-messes-with-linux-partition/f3584285-72b7-4f4e-8e7b-5a8b0eadbb72), I thought it might be a better idea to move Windows 7 to its own SSD, separating the two OSs onto their own drives.
I copied my Windows 7 partition to the new SSD using GParted, but when I run "update-grub" from linux to add the new copy of Windows to the GRUB boot menu, it doesn't find the new copy, only the old one. It makes no difference whether the new SSD Windows partition is mounted or not.
What additional steps have I missed here? I only have a vague understanding of how a computer boots up.
Also, is this approach even the best one? If Windows 7 actually doesn't pose any risk to Linux (it's given me no problems for a couple of years), then simply using the new drive as a D: drive for Windows (and some additional space for Linux) would probably be a better idea.
EDIT: I've added a few links to stories of Windows 10 corrupting partition tables to back-up my rationale for moving Windows to its own drive. However, if Windows 7 poses no risk, please feel free to tell me my approach is unnecessary.
dual-boot grub2 partitioning windows-7 ssd
I have a dual boot Windows 7 and Ubuntu 14.04 machine both using a 500 Gig SSD. I want to increase the space available to Windows 7 by adding another SSD. Since there seem to be some stories about Windows updates nuking other partitions on the drive it occupies (https://forum.level1techs.com/t/solved-windows10-anniversary-nuked-my-linux-partition-table/110271 , https://www.partitionwizard.com/partitionmanager/partition-disappears-in-win-10-anniversary-update.html , https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-update-messes-with-linux-partition/f3584285-72b7-4f4e-8e7b-5a8b0eadbb72), I thought it might be a better idea to move Windows 7 to its own SSD, separating the two OSs onto their own drives.
I copied my Windows 7 partition to the new SSD using GParted, but when I run "update-grub" from linux to add the new copy of Windows to the GRUB boot menu, it doesn't find the new copy, only the old one. It makes no difference whether the new SSD Windows partition is mounted or not.
What additional steps have I missed here? I only have a vague understanding of how a computer boots up.
Also, is this approach even the best one? If Windows 7 actually doesn't pose any risk to Linux (it's given me no problems for a couple of years), then simply using the new drive as a D: drive for Windows (and some additional space for Linux) would probably be a better idea.
EDIT: I've added a few links to stories of Windows 10 corrupting partition tables to back-up my rationale for moving Windows to its own drive. However, if Windows 7 poses no risk, please feel free to tell me my approach is unnecessary.
dual-boot grub2 partitioning windows-7 ssd
dual-boot grub2 partitioning windows-7 ssd
edited Feb 3 at 20:35
PhilipC
asked Feb 2 at 23:57
PhilipCPhilipC
112
112
A simple copy to another drive will not create another operating OS. Simple copies will copy all of the files, but the copy will not set up the boot configuration so the 'copy' will not be seen as a working OS. The best way to do this is to do a new Windows 7 install on the new SSD and then copy over the files needed for your current setup (programs, documents, pics, etc). There will be some additional work to set up your desktop (prog. shortcuts).
– Craig
Feb 3 at 4:20
If you want to add the full new SSD to Windows, don't do anything! Just add it to the system and create a new drive letter under Windows and then move Windows Data over to that new drive. (off-topic here, so leaving a comment instead of an answer)
– Fabby
Feb 3 at 8:55
@Craig Although that would work, it seems a shame to go to all the effort of doing a reinstall just to obtain a bootable installation. Surely there is a more direct way of making a clone bootable?
– PhilipC
Feb 3 at 20:27
@Fabby This is very easy to do, but I'm exploring the possibility of moving all of Windows to its own drive because of some reports of Windows corrupting partition tables during updates. Microsoft themselves recommend "other operating systems" go on separate drives (answers.microsoft.com/en-us/windows/forum/…) However, if there is no risk of Windows corrupting Linux, I will just add the drive as a data drive and not move Windows. Is this actually a risk with Windows 7?
– PhilipC
Feb 3 at 20:32
Windows corrupting other OSes will happen regardless of whether it has its own boot drive or not. That's why we have boot-repair
– Fabby
Feb 3 at 20:59
|
show 1 more comment
A simple copy to another drive will not create another operating OS. Simple copies will copy all of the files, but the copy will not set up the boot configuration so the 'copy' will not be seen as a working OS. The best way to do this is to do a new Windows 7 install on the new SSD and then copy over the files needed for your current setup (programs, documents, pics, etc). There will be some additional work to set up your desktop (prog. shortcuts).
– Craig
Feb 3 at 4:20
If you want to add the full new SSD to Windows, don't do anything! Just add it to the system and create a new drive letter under Windows and then move Windows Data over to that new drive. (off-topic here, so leaving a comment instead of an answer)
– Fabby
Feb 3 at 8:55
@Craig Although that would work, it seems a shame to go to all the effort of doing a reinstall just to obtain a bootable installation. Surely there is a more direct way of making a clone bootable?
– PhilipC
Feb 3 at 20:27
@Fabby This is very easy to do, but I'm exploring the possibility of moving all of Windows to its own drive because of some reports of Windows corrupting partition tables during updates. Microsoft themselves recommend "other operating systems" go on separate drives (answers.microsoft.com/en-us/windows/forum/…) However, if there is no risk of Windows corrupting Linux, I will just add the drive as a data drive and not move Windows. Is this actually a risk with Windows 7?
– PhilipC
Feb 3 at 20:32
Windows corrupting other OSes will happen regardless of whether it has its own boot drive or not. That's why we have boot-repair
– Fabby
Feb 3 at 20:59
A simple copy to another drive will not create another operating OS. Simple copies will copy all of the files, but the copy will not set up the boot configuration so the 'copy' will not be seen as a working OS. The best way to do this is to do a new Windows 7 install on the new SSD and then copy over the files needed for your current setup (programs, documents, pics, etc). There will be some additional work to set up your desktop (prog. shortcuts).
– Craig
Feb 3 at 4:20
A simple copy to another drive will not create another operating OS. Simple copies will copy all of the files, but the copy will not set up the boot configuration so the 'copy' will not be seen as a working OS. The best way to do this is to do a new Windows 7 install on the new SSD and then copy over the files needed for your current setup (programs, documents, pics, etc). There will be some additional work to set up your desktop (prog. shortcuts).
– Craig
Feb 3 at 4:20
If you want to add the full new SSD to Windows, don't do anything! Just add it to the system and create a new drive letter under Windows and then move Windows Data over to that new drive. (off-topic here, so leaving a comment instead of an answer)
– Fabby
Feb 3 at 8:55
If you want to add the full new SSD to Windows, don't do anything! Just add it to the system and create a new drive letter under Windows and then move Windows Data over to that new drive. (off-topic here, so leaving a comment instead of an answer)
– Fabby
Feb 3 at 8:55
@Craig Although that would work, it seems a shame to go to all the effort of doing a reinstall just to obtain a bootable installation. Surely there is a more direct way of making a clone bootable?
– PhilipC
Feb 3 at 20:27
@Craig Although that would work, it seems a shame to go to all the effort of doing a reinstall just to obtain a bootable installation. Surely there is a more direct way of making a clone bootable?
– PhilipC
Feb 3 at 20:27
@Fabby This is very easy to do, but I'm exploring the possibility of moving all of Windows to its own drive because of some reports of Windows corrupting partition tables during updates. Microsoft themselves recommend "other operating systems" go on separate drives (answers.microsoft.com/en-us/windows/forum/…) However, if there is no risk of Windows corrupting Linux, I will just add the drive as a data drive and not move Windows. Is this actually a risk with Windows 7?
– PhilipC
Feb 3 at 20:32
@Fabby This is very easy to do, but I'm exploring the possibility of moving all of Windows to its own drive because of some reports of Windows corrupting partition tables during updates. Microsoft themselves recommend "other operating systems" go on separate drives (answers.microsoft.com/en-us/windows/forum/…) However, if there is no risk of Windows corrupting Linux, I will just add the drive as a data drive and not move Windows. Is this actually a risk with Windows 7?
– PhilipC
Feb 3 at 20:32
Windows corrupting other OSes will happen regardless of whether it has its own boot drive or not. That's why we have boot-repair
– Fabby
Feb 3 at 20:59
Windows corrupting other OSes will happen regardless of whether it has its own boot drive or not. That's why we have boot-repair
– Fabby
Feb 3 at 20:59
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1115123%2fmove-windows-7-to-another-drive-on-dual-boot-machine%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1115123%2fmove-windows-7-to-another-drive-on-dual-boot-machine%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
A simple copy to another drive will not create another operating OS. Simple copies will copy all of the files, but the copy will not set up the boot configuration so the 'copy' will not be seen as a working OS. The best way to do this is to do a new Windows 7 install on the new SSD and then copy over the files needed for your current setup (programs, documents, pics, etc). There will be some additional work to set up your desktop (prog. shortcuts).
– Craig
Feb 3 at 4:20
If you want to add the full new SSD to Windows, don't do anything! Just add it to the system and create a new drive letter under Windows and then move Windows Data over to that new drive. (off-topic here, so leaving a comment instead of an answer)
– Fabby
Feb 3 at 8:55
@Craig Although that would work, it seems a shame to go to all the effort of doing a reinstall just to obtain a bootable installation. Surely there is a more direct way of making a clone bootable?
– PhilipC
Feb 3 at 20:27
@Fabby This is very easy to do, but I'm exploring the possibility of moving all of Windows to its own drive because of some reports of Windows corrupting partition tables during updates. Microsoft themselves recommend "other operating systems" go on separate drives (answers.microsoft.com/en-us/windows/forum/…) However, if there is no risk of Windows corrupting Linux, I will just add the drive as a data drive and not move Windows. Is this actually a risk with Windows 7?
– PhilipC
Feb 3 at 20:32
Windows corrupting other OSes will happen regardless of whether it has its own boot drive or not. That's why we have boot-repair
– Fabby
Feb 3 at 20:59