If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was
from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. |
Ads |
#2
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
"BobH" wrote in message ... I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. http://www.askvg.com/tip-dual-boot-b...ndows-78-1-os/ |
#3
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
On 05/08/2015 14:14, Live wrote:
"BobH" wrote in message ... I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. http://www.askvg.com/tip-dual-boot-b...ndows-78-1-os/ Yes, I read that information prior to doing anything,but it does not say that 1 drive should be disconnected or not. It does seem to say that you should just install windows 10 as a clean installation on the 2nd drive, but is that with or without the 1st drive connected?? |
#4
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
BobH wrote:
On 05/08/2015 14:14, Live wrote: "BobH" wrote in message ... I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. http://www.askvg.com/tip-dual-boot-b...ndows-78-1-os/ Yes, I read that information prior to doing anything,but it does not say that 1 drive should be disconnected or not. It does seem to say that you should just install windows 10 as a clean installation on the 2nd drive, but is that with or without the 1st drive connected?? Cloning is a separate issue from dual-booting. There is some (stinking) disk identifier, that if duplicated by cloning, the second disk becomes "Offline". You must correct this, so each disk has a unique identifier. The BCD contains identifiers (GUID) which identify the relationship of C: to the partition that handles the booting (System Reserved). You might easily manage to create duplicate identifiers there as well. Now, imagine winload.exe has scanned the two drives and has duplicates all over the place, and is being asked to "pick one". Well, it can't. Because it might make a mistake, and record the state information for the session on an unexpected disk (not the bootup the user desired). Open a Command Prompt (Administrator) window via right-click of Start menu, and type bcdedit to see some of the identifiers the boot manager uses for booting. Somehow, you need a means to review the various disk identifiers, to prevent problems. Things like VolumeID, I don't think those hurt. Things like disk labels (having two "WinXP" labeled disks), those don't hurt either. But there are other numbers stored on the disk or partitions, which do matter. This one is for disk signature (solve "offline" disk drive showing in Disk Management). http://www.howtohaven.com/system/cha...ignature.shtml Paul |
#5
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
On 05/08/2015 16:12, Wolf K wrote:
On 2015-08-05 06:15, BobH wrote: I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. You can easily dual boot _different_ OSs, but it looks like you can't dual boot _identical_ OSs. Or so I infer from your curious story. Ok, it looks like I will be installing win10 on the 2nd ssd with the 1st ssd disconnected. Then when that is complete, just connect both up again and see what happens. Thanks for the clarification. |
#6
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
Once in the past I was able to make a 4 windows boot system with two hard
disks and same windows key. "BobH" escreveu na mensagem ... I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. |
#7
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
BobH wrote on 08/05/2015 6:15 AM:
I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. So you're planning on using one single Win 8.1 license to ugprade one SSD to 10, and use that same 8.1 license on the same device but a differnt SSD ? -- ...winston msft mvp windows experience |
#8
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
On 06/08/2015 07:05, . . .winston wrote:
BobH wrote on 08/05/2015 6:15 AM: I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. So you're planning on using one single Win 8.1 license to ugprade one SSD to 10, and use that same 8.1 license on the same device but a differnt SSD ? Actually no, that is not what I was meaning to do, as I said above that my initial plan was to put windows 10 on the 2nd ssd Last week I upgraded the 1st ssd with windows 8.1 to windows 10. After a short while , because my 2nd monitor was not supported by the drivers for my graphics card in windows 10, I reverted back to windows 8.1. Now with regards to my 2nd ssd which had windows 8.1 on, my intention was to upgrade that to windows 10. The reason for doing so was to find out if by a slight change I made with the 2nd monitor, would it be seen / recognised by windows 10. Instead of connecting to the vga port on the graphics card I connected it to the vga port on the motherboard, and I was hoping that it would be seen by windows 10 once I had upgraded the win8.1 system. |
#9
|
|||
|
|||
Strange thing happening with 2 copies of win 8.1
BobH wrote on 08/06/2015 4:12 AM:
On 06/08/2015 07:05, . . .winston wrote: BobH wrote on 08/05/2015 6:15 AM: I have 2 ssd's each with a bootable copy of win8.1. The 2nd copy was from an image of the 1st copy, so both ssd's have exactly the same programs etc. I disconnected the 1st copy/ssd when I restored the image onto the 2nd ssd, just to be sure it was the correct drive for the image. Now with both ssd's connected, I can boot to the 1st copy of win8.1, but if I choose to boot the 2nd copy or ssd, it will not boot with both ssd's connected and I have to disconnect the 1st ssd or copy of win8.1. The error message is something like: Ooops, it looks like something went wrong or similar, and then says, we are collecting some whatever and sticks on 0%. But as soon as I disconnect the 1st drive the 2nd one boots ok! My initial plan was to put windows 10 on the 2nd ssd, and have a dual boot between that and windows 8.1. Given with what happened it doesn't look like I can have a dual boot systems Any ways around it, or should I have gone about it a different way. So you're planning on using one single Win 8.1 license to ugprade one SSD to 10, and use that same 8.1 license on the same device but a differnt SSD ? Actually no, that is not what I was meaning to do, as I said above that my initial plan was to put windows 10 on the 2nd ssd Last week I upgraded the 1st ssd with windows 8.1 to windows 10. After a short while , because my 2nd monitor was not supported by the drivers for my graphics card in windows 10, I reverted back to windows 8.1. Now with regards to my 2nd ssd which had windows 8.1 on, my intention was to upgrade that to windows 10. The reason for doing so was to find out if by a slight change I made with the 2nd monitor, would it be seen / recognised by windows 10. Instead of connecting to the vga port on the graphics card I connected it to the vga port on the motherboard, and I was hoping that it would be seen by windows 10 once I had upgraded the win8.1 system. As I understood the first post..the 8.1 on the second SSD was a clone of the first...which would be the same license. Additionally you noted the SSD was installed on the same device (you said 'both SSD's connected")....which appears to still be a 'yes' to my question - using the same license twice (once to upgrade to 10 now rolled back to 8.1 and also to use again as the license to upgrade to Win10 on the second SSD) on the same physical device. - afiak....if you use the 8.1 license to upgrade to 10, you can't continue to use it elsewhere on another device (the second SSD)...as noted before...technically feasible isn't the same as licensing. -- ...winston msft mvp windows experience |
Thread Tools | |
Display Modes | Rate This Thread |
|
|