Using Universal Restore to Move to a New Computer
I'm buying a new computer and intend to use Universal Restore to transfer my system from my current computer to the new one, and have some questions.
I am moving a Windows 8.1 system upgraded to Windows 10 during the free period last year. I assume it doesn't care what Windows system it's moving but I thought it prudent to ask:
- Is there any problem with this?
In going through the media builder steps it want's me to use Linux based media.
2. Does that make sense?
It asks me to specify Linux Kernel parameters
3. I don't know what that means so I'm skiping that step -- correct?
It asks me what components I want to add and I chose Universal Restore 64-bit with UEFI. My Windows is 64bit and, as far as I know, all recent machines use UEFI.
4. Is that correct?
It asks me to add mass storage device drivers. I don't have any so I skipped that step too.
5. Will this work?
In the help file it carries on and carries on about drivers for the new machine. I couldn't figure out the best place to put them but I currently plan to put them on the same USB drive as the backup file.
6. Will that work?
I assume Universal Restore will move Windows and all my installed programs just as if I were restoring to my original hard drive. So, I will be up and going right where I left off.
7. Is that correct?
I am moving a Windows 8.1 system upgraded to Windows 10 during the free period last year. I assume it doesn't care what Windows system it's moving but I thought it prudent to ask:
- Is there any problem with this?
Yes, there could be. OEM licenses (those that come with a computer) are not transferable. However, Windows 10 is a new license scheme and as long as you have activated Windows 10 on the new system, and it is the same version as the old one (home or pro) and has been activated on the new system as well, you should be able to move the OS from the old computer to the new one and it will license correctly.
I don't follow this. Are you saying if I were moving my original 8.1 system the transfer would not have worked, but since I will be using the Win10 upgrade it should work?
When you say "as long as you have activated Windows 10 on the new system," does that mean I have to have a new copy of Win10 installed on the new system before beginning the transfer? No where in all the stuff I've read and watched about doing this have I seen that stated or even suggested until your remark.
It asks me what components I want to add and I chose Universal Restore 64-bit with UEFI. My Windows is 64bit and, as far as I know, all recent machines use UEFI.
4. Is that correct?
I would pick that. I think you're using the wrong media builder. You're using the Universal restore media builder. Build the rescue media from Acronis directly and it will do this stuff for you.
Again, I don't understand what it means when you say, "I think you're using the wrong media builder. " When I select the item ACRONIS UNIVERSAL RESTORE on the Tools menu I get a screen with the heading Acronis Bootable Media Builder, this choice is on the 4th screen (see screen capture below) I'm under the impression the Bootable Rescue Media is only used to restore the image file.
UR is a tool to generalize drivers, that's it - it doesn't help you backup or restore an image.
I think I worded my question poorly. I understand I have to restore the image independently and then apply the Universal Restore. I'm trying to ask if after all this is complete will it have moved my Windows OS and all my installed programs such that I pick up right where I left off?
I don't follow this. Are you saying if I were moving my original 8.1 system the transfer would not have worked, but since I will be using the Win10 upgrade it should work?When you say "as long as you have activated Windows 10 on the new system," does that mean I have to have a new copy of Win10 installed on the new system before beginning the transfer? No where in all the stuff I've read and watched about doing this have I seen that stated or even suggested until your remark.
What type of Windows license do you have? If this is an OEM license, i.e. one branded for Dell, HP, Lenovo etc then these licenses are tied to the hardware where they were first activated and are not transferable to a new system. If you have a full Retail Microsoft Windows license then this can be moved to new hardware.
With Windows 10, most licenses are activated based on the hardware signature of the computer, so what Bobbo was saying, was that if you new computer comes with a valid Windows 10 license that has been activated for that hardware signature, then you should be able to move your old Windows 10 OS to that new hardware, provided both are using the same version of Window 10 (i.e. both Home Premium versions) and Windows will pick up the license / activation for the hardware signature of the new computer.
Again, I don't understand what it means when you say, "I think you're using the wrong media builder. " When I select the item ACRONIS UNIVERSAL RESTORE on the Tools menu I get a screen with the heading Acronis Bootable Media Builder, this choice is on the 4th screen (see screen capture below) I'm under the impression the Bootable Rescue Media is only used to restore the image file.
There are two different media builder tools that you can use here. There is the main Rescue Media Builder which can build either the standard, Linux based, Rescue Media or the WindowsPE version of the same, and there is also a separate Universal Restore Media Builder which can also include the standard Rescue Media applications.
The main Rescue Media does need to be used to restore the backup of your old Windows OS to the new hardware, but it should not matter which actual media you use here provided that both types will offer you the Acronis True Image 64-bit application, and you are booting the media in UEFI mode to suit your computer systems.
I understand I have to restore the image independently and then apply the Universal Restore. I'm trying to ask if after all this is complete will it have moved my Windows OS and all my installed programs such that I pick up right where I left off?
The initial Restore of your Windows OS to the new computer will have moved all your Windows OS and installed programs etc, then Universal Restore will be used to prepare that restore OS to work with any different hardware found in the new computer.
Whether you can just pick up right where you left off really depends if any issues are raised when you attempt to boot the restored Windows 10 OS on the new hardware. You should expect to see messages about new hardware found where Windows will try to find better device drivers for hardware where generic drivers are currently used. You may also see activation messages if any of your applications are activated by the hardware signature of the old computer, which again comes down to how those applications are licensed and if they can be moved etc.
Thanks for your reply. I'm getting there.
What type of Windows license do you have? If this is an OEM license, i.e. one branded for Dell, HP, Lenovo etc then these licenses are tied to the hardware where they were first activated and are not transferable to a new system. If you have a full Retail Microsoft Windows license then this can be moved to new hardware.
The source computer is a Lenovo and the destination is a custom build. As I said earlier, there was no mention anywhere of needing a copy of Windows on the new computer. If I must have a different copy of Windows 10 on the new build, I guess I would use ==>this one.
There are two different media builder tools that you can use here. There is the main Rescue Media Builder which can build either the standard, Linux based, Rescue Media or the WindowsPE version of the same, and there is also a separate Universal Restore Media Builder which can also include the standard Rescue Media applications.
What is the advantage of putting the Rescue Media on the Universal Restore (in my case) CD? The convenience of not having to use two disks and two boots?
Jim, the requirement for a licensed copy of Windows 10 is one imposed by Microsoft, not by Acronis. The version of Windows 10 should be the same as you have on the Lenovo currently, so if that is Windows 10 Home the one on Amazon would be fine.
The only advantage of having the Rescue Media on the Universal Restore CD is just having the one CD, but this assumes that you can boot the new customer build computer from that same media, which is something that you will need to test to prove. As I stated earlier, there are the two types of media, one is based on a Linux distribution and will work on many systems but this will not work if the system used RAID as the SATA controller mode for the disk drive(s) as no RAID drivers are included in this media. The Windows PE media can be used in that case but will still need to have the Intel RST drivers injected for RAID support, which can be done by using the MVP Tool - Custom ATI WinPE Builder script (link below). The MVP Tool can also create USB or CD media with Windows PE and both types of media included, Rescue and AUR.
Yes, that oem version would work. You can get pro for $125 on Amazon too. However if your current Lenovo OS system is a home version, then get home again since you want to move the os from the old one to the new one. Basically, you would install the new license on the new build and activate it with Microsoft so the motherboard and license are stored with Microsoft for that motherboard. After that, you'd be able to restore your old system os and windows 10 would remain registered on the new system since the motherboard was previously registered with a valued windows 10 license.
Just remember that oem licenses are tied to the hardware so would basically be tied to your new main board (not transferable to another computer). If you got a full retail license, you'd have no problem moving that down the road to a new system or different motherboard. Oem is cheaper up front, but retail could save you money down the road.
http://www.tomshardware.com/forum/id-2727007/windows-pro-retail-windows…
Sorry to keep kicking this horse, but I don't like surprises in siturations like this.
I'm still worried about drivers for the new hardware. In reading on the Acronis website I get ==>this screen capture. It talks about drivers. I don't get that screen when creating the Universal Restore CD.
Assuming I don't need it and Universal Restore substitutes any necessary generic drivers to get started, when Windows boots up the first time, does it ask me where to find drivers or does it just take off hunting on its own?
Jim, please see KB 56637: Acronis True Image 2016: Restoring to Dissimilar Hardware with Acronis Universal Restore which goes through the processes needed for AUR and includes screen shots of the steps where drivers can be added to the media, if needed.
The key point about device drivers, as stated in the KB document, is that you do not have to add drivers immediately, but can do so later when applying AUR to the target system.
The main drivers that may be needed are the motherboard chipset drivers for your new build, plus any specific disk controller drivers.
Actually, that's where that screen capture comes from. So, that screen is in the use phase and not in the build phase?
Jim, the image you linked to was from the AUR application when it has been booted not from when an option is given during the AUR media creation, which is shown in step 6. of the previous expanded section.
I would not add any drivers there. Run ur to generalize drivers only and reboot. You only need to add drivers if you have special storage controllers like if you're using a special raid controller add on card. All of your other drivers will get installed when you boot into the recovered windows system.
your biggest concern for transferring the OS is making sure the bios is configured correctly on the new machine. The sata mode needs to match the old one. Secureboot in the bios needs to be disabled. If the old OS is legacy, then you need to make sure the new bios has csm/legacy enabled. If the old OS is legacy, you need to make sure you boot the Acronis rescue media in legacy mode to do the restore - this is similar to how you need to boot a windows installer if you want to have a legacy or UEFI install.
All of the bios settings and configs are on the user as no recovery media can change or set those for you. This is the most difficult part because each motherboard and firmware is different in the available bios options and settings.
And just when I thought I saw light at the end of the tunnel, it may be an oncoming desil.
your biggest concern for transferring the OS is making sure the bios is configured correctly on the new machine. The sata mode needs to match the old one. Secureboot in the bios needs to be disabled. If the old OS is legacy, then you need to make sure the new bios has csm/legacy enabled. If the old OS is legacy, you need to make sure you boot the Acronis rescue media in legacy mode to do the restore - this is similar to how you need to boot a windows installer if you want to have a legacy or UEFI install.
My present BIOS is very simplistic. It is set to IDE mode (see attached). I don't see anything called Sureboot. I don't know what a leagacy OS is. The source operating system is Windows 10. All my drives are SATA. My C: drive is SSD and the new computer ports are mostly SATA III. Somewhere I got the advice that on a fresh install of 10, I should set the BIOS to UEFI and SATA drives to AHCI
Jim, it is unlikely that your new computer will offer an option to boot the SATA controller in IDE mode and this will be a problem if your Lenovo computer cannot boot the SATA controller in AHCI mode.
Legacy is about the BIOS not the OS in this context. Your second image shows that the Lenovo is capable of operating in both Legacy and UEFI BIOS modes, but the key question arising from this information, is how is your Windows OS actually starting on this system.
See webpage: Check if your PC uses UEFI or BIOS to help find which is actually used. Alternatively, from within Windows Disk Management on the Lenovo computer, check to see if you have an EFI (UEFI) partition shown, as this will give an indication too.
If your Lenovo does boot in Legacy mode, as suggested by your screenshot showing 'Legacy first' in the BIOS settings, then your new computer will also need to support booting the OS in the same mode!
When I make an image it shows a LRS_ESP partition which I think means it uses UEFI. But, it will not boot in SATA mode.
You need to prep the OS before changing machines. Backup your OS "as is" before you do anything. That is your fallback point, just in case.
Then perform the steps outlined here on the old machine and switch to AHCI and immediately power off (shutdown) without booting to the OS.
You would need to be able to then take a new image of the machine after that and that is what you would restore to the new machine onto a SATA SSD or SATA hard drive - hope you're getting an SSD for this new machine for your OS - that is the biggest upgrade you can make for daily performance.
Your current OS install is almost certainly legacy/csm if you're still using IDE, but do confirm with the link Steve gave you.
For the initial transfer, to the new hardware, you'll want to keep it simple (as possible) and try to restore in CSM\legacy mode on any new hardware so your new bios will need to support CSM\legacy (most home builder boards do - it's just a matter of figuring out where those settings are and getting it correct). Check this thread for the differences in what booting the rescue media in legacy vs UEFI looks like. Your new board should have a one-time boot menu where you can specifically pick uefi or legacy booting from the rescue media if the bios is configured correctly. The example is from a Dell, but it's just to point out that you should be able to see the difference in the bios of the device you are booting and to verify what you see when booting Acronis rescue media once you've picked a boot option. https://forum.acronis.com/forum/121829#comment-378318
Once the image has been restored, check the bios boot order and ensure that the legacy option for the new disk is listed first. Verify CSM\legacy is enabled, verify secure boot is disabled.
Try to boot it up - you might find it just works since Windows 10 is good at handling driver changes and SATA modes. If not and you get a BSOD, then boot UR in the correct mode (assuming legacy mode here) and run it. Ignore any driver warnings if you get any. Don't worry about adding drivers. You just want to generalize the existing drivers from your old OS install to make it vanilla so that it hopefully boots on the new hardware.
Assuming it boots, it should start downloading Win10 compatible drivers for the new hardware. You may want to grab the Win10 drivers from your bios website in advance - esepcially if you have a cutom NIC (ethernet), like a Killer gaming NIC - so you can at least get on the net to start downloading others.
It's do-able. The OS transfer with Acronis (or any backup and restore product) is the simple part. It's the bios settings that are the most difficult these days since they vary so much with UEFI now.
When I make an image it shows a LRS_ESP partition which I think means it uses UEFI. But, it will not boot in SATA mode.
Could you take some screenshots of your OS in disk management? The paritions layout should help identify how your OS was installed. Also, when you run "system information", what does the bios mode show? UEFI or Legacy?
Could you take some screenshots of your OS in disk management? The paritions layout should help identify how your OS was installed. Also, when you run "system information"
perform the steps outlined here on the old machine and AHCI and immediately power off (shutdown) without booting to the OS.
I'm confused. You say "switch to AHCI and immediately power off (shutdown) without booting." The procedure says to boot back into Windows after changing to AHCI, turn off safe mode and reboot again.
I'm a little reluctant to try this. I tried changing IDA to SATA once and the system wouldn't start. It began giving various failure messages and then began automatically rebooting over and over. I thought I had lost the whole system. This was not in safe mode, but once I went into safe mode on this machine and a lot of things went wrong -- been too long ago for me to remember. I also thought I'd lost the machine at that point too and never chanced safe mode again. I've even forgotten how to access it.
Oh yes, the C: drive you see in that screen capture is a Samsung SSD I got a while back because a friend raved about how it sped up his machine. I never saw any gain from it.
I can't really see what's on those partitions in your picture since they are not expanded out. You fave a lot of partitions though, which is suggesting UEFI but can't tell. What does system information show for the bios mode?
so, you're using a Samsung ssd in ide mode? No, you won't see much performance here because ide is slow. I didn't think it would even let you use ide mode on a sata drive, but I guess that really depends on the controller. Oh it's seeing the drive in that config, then you'd only have to take the initial backup for safety and then follow the links instructions.
either way, you'll have to take a leap of faith and do it or give up and start fresh on your new system. You can reduce risk by...
1. Taking a full backup before and after the sata mode change
2. Restoring and testing those images to a different drive than the original drives so you can test before overwriting or making changes to any original data. Typically if you have good, full disk backups you can just restore from those and try again if need be, but if you don't have to test with the primary drives for your restored or modifications, if things go bad, then you can return to the original drive as well since it would have been left alone to begin with.
Jim, I would suggest creating an Acronis System Report and posting it to the forum, as this would include MSINFO32 output showing exactly what your partitions are, how your system boots BIOS wise etc.
I assume you are mostly interested in the hard disk info:
DA-API report version 3
PS Speed IFace Hs-Bs-Tg Model
Num NT L9NO Size FSsize Free FS Type Label ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
1- d(1) GPT 233G 132M ATA 0-0-0 Samsung SSD 850 EVO 250GB
MBR ------
GPTpri -----v
129M unallc ------
-1 ---- 1G 1G 621M NTFS 27 Windows RE H WINRE_DRV.. --c--V
-2 ---- 260M 260M 230M FAT32 EF EFI SYSTEM_DRV. --c--V
-3 ---- 500M 500M 236M FAT32 07 NTFS, HPFS LRS_ESP.... --c--V
-4 --CC 206G 206G 80G NTFS 07 NTFS, HPFS Windows8_OS --c--V
-5 ---- 350M 350M 58M NTFS 27 Windows RE H ........... --c--V
-6 ---- 24G 24G 12G NTFS 27 Windows RE H PBR_DRV.... --c--V
GPTbck ------
2- d(?) MBR 932G 13M ATA 0-0-0 ST31000524AS
MBR -----v
-1 p(1) --DF 932G 932G 663G NTFS 07 NTFS, HPFS DATADISK... --c--V
3- d(?) MBR 1.4T 11M USB 0-0-0 asmedia ASMT1153e 0
MBR -----v
7.8M unallc ------
-2 EPT 05 Extended A-----
-5 p(1) --ED 1.4T 1.4T 696G NTFS 07 NTFS, HPFS ........... --c--V
2.5M unallc ------
Firmware: UEFI x64
OS: Windows
Free letters: ----EFGH----MN-PQRSTUVW---
Disk 1 properties:
BIOS number: 0x81
Geometry: 30402 255 63 LSS: 512, PSS: 4096, LSO: 0
Total sectors: 488397168 (0x1D1C5970)
Device name: "\Device\Ide\IdeDeviceP1T0L0-1"
GPT GUID: D9FED0CA-8B6D-4E38-B122-69A4E0B54DA8
HW serial: "S2R5NX0H470636R "
Sys name: "\Device\Ide\IdeDeviceP1T0L0-1"
Disk 2 properties:
Geometry: 121601 255 63 LSS: 512, PSS: 512, LSO: 0
Total sectors: 1953516911 (0x74704D6F)
Device name: "\Device\Ide\IdeDeviceP2T0L0-2"
HW serial: " 5VP8HNZN"
Sys name: "\Device\Ide\IdeDeviceP2T0L0-2"
Disk 3 properties:
Geometry: 182402 255 63 LSS: 512, PSS: 512, LSO: 0
Total sectors: 2930277168 (0xAEA87B30)
Device name: "\Device\0000003e"
HW serial: "A11987654321"
Sys name: "\Device\0000003e"
1F0 F8 07 F9 07 FA 07 FB 07 FC 07 FD 07 FE 07 FF 07 ø.ù.ú.û.ü.ý.þ.ÿ.
Unallocated 3-*:
Sector 2930272065 (0xAEA86741) (182401 0 1) - Sector 2930272096 (0xAEA86760) (182401 0 32) - All 00
MBR 1-*:
First sector: 0 (0x0) (0 0 1)
Table extended structure
Extended boot sector: 0
Extended hidden partitions: 00 (Unused)
00 (Unused)
00 (Unused)
00 (Unused)
Extended boot disk: 0x00
Extended patch flags: FAT16(-) MS-DOS7+(-) FAT32(-) OS/2(-)
Extended OS/2 patch: 0x00
Extended checksum (0x00): 0x00
Extended size (14): 0
NT signature: 0x4150E9AC
Extended serial number: 0x0000
i f Start C H S End C H S Start Size Type
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
0 - 0 0 2 1023 254 63 1 488397167 EE (GPT)
- 0 0 2 1023 254 63 1 488397167 EE (GPT)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
1 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
2 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
3 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
Boot sign (0x0AA55): 0xAA55
Meta 1-*: of type 00 (Unused)
First sector: 1 (0x1) (0 0 2)
Table extended structure
Extended boot sector: 0
Extended hidden partitions: 00 (Unused)
00 (Unused)
00 (Unused)
00 (Unused)
Extended boot disk: 0x00
Extended patch flags: FAT16(-) MS-DOS7+(-) FAT32(-) OS/2(-)
Extended OS/2 patch: 0x00
Extended checksum (0x00): 0x00
Extended size (14): 0
NT signature: 0x00000000
Extended serial number: 0x0000
i f Start C H S End C H S Start Size Type
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
0 - 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
1 - 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
2 - 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
3 - 0 0 0 0 0 0 0 0 00 (Unused)
Boot sign (0x0AA55): 0x0000
Unallocated 1-*: of size 129M
First sector: 34 (0x22) (0 0 35)
Last sector: 264191 (0x407FF) (16 113 33)
Total sectors: 264158 (0x407DE)
Partition 1-1: of type 27 (Windows RE Hidden, PQ, MirOS) GPT type DE94BBA4-06D1-4D40-A16A-BFD50179D6AC and size 1G
First sector: 264192 (0x40800) (16 113 34)
Last sector: 2312191 (0x2347FF) (143 236 29)
Total sectors: 2048000 (0x1F4000)
NTFS bootsector structure:
Jump code: 0xEB 0x52 0x90
File system name: NTFS
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors (0): 0
FAT copies (0): 0
Root folder items (0): 0
Total sectors (0): 0
Media ID: 0xF8
FAT size (0): 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 264192
Big total sectors (0): 0
Hard disk: 0x80
Reserved: 0x00 0x0080
Big total sectors: 2047992
MFT cluster: 83166
MFTmirr cluster: 2
MFT record size: -10
Index buffer size: 1
Serial number: FE7A-5CF6-7A5C-ACE1
Boot signature (0AA55h): 0xAA55
Partition 1-2: of type EF (EFI) GPT type C12A7328-F81F-11D2-BA4B-00A0C93EC93B and size 260M
First sector: 2312192 (0x234800) (143 236 30)
Last sector: 2844671 (0x2B67FF) (177 18 33)
Total sectors: 532480 (0x82000)
FAT32 bootsector structure:
Jump code: 0xEB 0x58 0x90
OEM ID: MSDOS5.0
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors: 34
FAT copies: 2
Root folder items: 0
Total sectors: 0
Media ID: 0xF8
FAT size: 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 2312192
Big total sectors: 532480
FAT size: 519
Flags: 0x0000
File system version: 0.0
First cluster of root: 2
FS info sector (1): 1
Backup sector (6): 6
Reserved: 0x00000000 0x00000000 0x00000000
Hard disk: 0x80
Reserved: 0x01
Extension signature: 0x29
Serial number: C05E-545D
Volume label: NO NAME
File system name: FAT32
Boot signature (0AA55h): 0xAA550000
Clusters from FAT: 66430
Clusters from Data: 66426
Partition 1-3: of type 07 (NTFS, HPFS) GPT type BFBFAFE7-A34F-448A-9A5B-6213EB736C22 and size 500M
First sector: 2844672 (0x2B6800) (177 18 34)
Last sector: 3868671 (0x3B07FF) (240 207 31)
Total sectors: 1024000 (0xFA000)
FAT32 bootsector structure:
Jump code: 0xEB 0x58 0x90
OEM ID: MSDOS5.0
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors: 34
FAT copies: 2
Root folder items: 0
Total sectors: 0
Media ID: 0xF8
FAT size: 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 2844672
Big total sectors: 1024000
FAT size: 999
Flags: 0x0000
File system version: 0.0
First cluster of root: 2
FS info sector (1): 1
Backup sector (6): 6
Reserved: 0x00000000 0x00000000 0x00000000
Hard disk: 0x80
Reserved: 0x00
Extension signature: 0x29
Serial number: 1E60-412B
Volume label: NO NAME
File system name: FAT32
Boot signature (0AA55h): 0xAA550000
Clusters from FAT: 127870
Clusters from Data: 127746
Partition 1-4: of type 07 (NTFS, HPFS) GPT type EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 and size 206G
First sector: 3868672 (0x3B0800) (240 207 32)
Last sector: 436467711 (0x1A03F7FF) (27168 218 58)
Total sectors: 432599040 (0x19C8F000)
NTFS bootsector structure:
Jump code: 0xEB 0x52 0x90
File system name: NTFS
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors (0): 0
FAT copies (0): 0
Root folder items (0): 0
Total sectors (0): 0
Media ID: 0xF8
FAT size (0): 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 3868672
Big total sectors (0): 0
Hard disk: 0x80
Reserved: 0x00 0x0080
Big total sectors: 432599032
MFT cluster: 750824
MFTmirr cluster: 2
MFT record size: -10
Index buffer size: 1
Serial number: E266-628B-6662-5FF1
Boot signature (0AA55h): 0xAA55
Partition 1-5: of type 27 (Windows RE Hidden, PQ, MirOS) GPT type DE94BBA4-06D1-4D40-A16A-BFD50179D6AC and size 350M
First sector: 436467712 (0x1A03F800) (27168 218 59)
Last sector: 437184511 (0x1A0EE7FF) (27213 121 44)
Total sectors: 716800 (0xAF000)
NTFS bootsector structure:
Jump code: 0xEB 0x52 0x90
File system name: NTFS
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors (0): 0
FAT copies (0): 0
Root folder items (0): 0
Total sectors (0): 0
Media ID: 0xF8
FAT size (0): 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 436467712
Big total sectors (0): 0
Hard disk: 0x80
Reserved: 0x00 0x0080
Big total sectors: 716792
MFT cluster: 24514
MFTmirr cluster: 2
MFT record size: -10
Index buffer size: 1
Serial number: 6842-805F-4280-343A
Boot signature (0AA55h): 0xAA55
Partition 1-6: of type 27 (Windows RE Hidden, PQ, MirOS) GPT type DE94BBA4-06D1-4D40-A16A-BFD50179D6AC and size 24G
First sector: 437184512 (0x1A0EE800) (27213 121 45)
Last sector: 488396799 (0x1D1C57FF) (30401 75 10)
Total sectors: 51212288 (0x30D7000)
NTFS bootsector structure:
Jump code: 0xEB 0x52 0x90
File system name: NTFS
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors (0): 0
FAT copies (0): 0
Root folder items (0): 0
Total sectors (0): 0
Media ID: 0xF8
FAT size (0): 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 437184512
Big total sectors (0): 0
Hard disk: 0x80
Reserved: 0x00 0x0080
Big total sectors: 51212280
MFT cluster: 711571
MFTmirr cluster: 2
MFT record size: -10
Index buffer size: 1
Serial number: 2632-5A66-325A-3ACF
Boot signature (0AA55h): 0xAA55
Meta 1-*: of type 00 (Unused)
First sector: 488397135 (0x1D1C594F) (30401 80 31)
Table extended structure
Extended boot sector: 6659
Extended hidden partitions: 00 (Unused)
00 (Unused)
00 (Unused)
00 (Unused)
Extended boot disk: 0x00
Extended patch flags: FAT16(-) MS-DOS7+(-) FAT32(-) OS/2(-)
Extended OS/2 patch: 0x00
Extended checksum (0xE3): 0x00
Extended size (14): 0
NT signature: 0x00000000
Extended serial number: 0x0000
i f Start C H S End C H S Start Size Type
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
0 - 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
1 - 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
2 - 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
3 - 0 0 0 0 0 0 0 0 00 (Unused)
Boot sign (0x0AA55): 0x0000
MBR 2-*:
First sector: 0 (0x0) (0 0 1)
Table extended structure
Extended boot sector: 1937339168
Extended hidden partitions: 74 (Scramdisk)
65 (NetWare 3.x+)
6D
00 (Unused)
Extended boot disk: 0x00
Extended patch flags: FAT16(-) MS-DOS7+(-) FAT32(-) OS/2(-)
Extended OS/2 patch: 0x00
Extended checksum (0x28): 0x62
Extended size (14): 39290
NT signature: 0xD897D2AB
Extended serial number: 0x0000
i f Start C H S End C H S Start Size Type
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
0 - 0 1 1 1023 254 63 63 1953516849 07 (NTFS, HPFS)
- 0 1 1 1023 254 63 63 1953516849 07 (NTFS, HPFS)
- 0 1 1 121600 204 60 63 1953516849
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
1 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
2 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
3 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
Boot sign (0x0AA55): 0xAA55
Partition 2-1: of type 07 (NTFS, HPFS) and size 932G
First sector: 63 (0x3F) (0 1 1)
Last sector: 1953516911 (0x74704D6F) (121600 204 60)
Total sectors: 1953516849 (0x74704D31)
NTFS bootsector structure:
Jump code: 0xEB 0x52 0x90
File system name: NTFS
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors (0): 0
FAT copies (0): 0
Root folder items (0): 0
Total sectors (0): 0
Media ID: 0xF8
FAT size (0): 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 63
Big total sectors (0): 0
Hard disk: 0x80
Reserved: 0x00 0x0080
Big total sectors: 1953516848
MFT cluster: 786432
MFTmirr cluster: 2
MFT record size: -10
Index buffer size: 1
Serial number: EC84-969F-8496-6BB8
Boot signature (0AA55h): 0xAA55
MBR 3-*:
First sector: 0 (0x0) (0 0 1)
Table extended structure
Extended boot sector: 0
Extended hidden partitions: 00 (Unused)
00 (Unused)
00 (Unused)
00 (Unused)
Extended boot disk: 0x00
Extended patch flags: FAT16(-) MS-DOS7+(-) FAT32(-) OS/2(-)
Extended OS/2 patch: 0x00
Extended checksum (0x00): 0x00
Extended size (14): 0
NT signature: 0xA42D966B
Extended serial number: 0x0000
i f Start C H S End C H S Start Size Type
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
0 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
1 A 1 0 1 1023 254 63 16065 2930256000 05 (Extended)
A 1 0 1 1023 254 63 16065 2930256000 05 (Extended)
- 1 0 1 1 0 1 16065 1
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
2 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
3 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
Boot sign (0x0AA55): 0xAA55
Unallocated 3-*: of size 7.8M
First sector: 1 (0x1) (0 0 2)
Last sector: 16064 (0x3EC0) (0 254 63)
Total sectors: 16064 (0x3EC0)
Meta 3-2: of type 05 (Extended)
First sector: 16065 (0x3EC1) (1 0 1)
Table extended structure
Extended boot sector: 0
Extended hidden partitions: 00 (Unused)
00 (Unused)
00 (Unused)
00 (Unused)
Extended boot disk: 0x00
Extended patch flags: FAT16(-) MS-DOS7+(-) FAT32(-) OS/2(-)
Extended OS/2 patch: 0x00
Extended checksum (0xF2): 0xF2
Extended size (14): 14
NT signature: 0x00000000
Extended serial number: 0x0000
i f Start C H S End C H S Start Size Type
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
0 - 0 1 1 1023 254 63 63 2930255937 07 (NTFS, HPFS)
- 0 1 1 1023 254 63 63 2930255937 07 (NTFS, HPFS)
- 1 1 1 182400 254 63 16128 2930255937
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
1 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
2 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
- - ---------- --- -- ---------- --- -- ---------- ---------- ----
3 - 0 0 0 0 0 0 0 0 00 (Unused)
- 0 0 0 0 0 0 0 0 00 (Unused)
Boot sign (0x0AA55): 0xAA55
Partition 3-5: of type 07 (NTFS, HPFS) and size 1.4T
First sector: 16128 (0x3F00) (1 1 1)
Last sector: 2930272064 (0xAEA86740) (182400 254 63)
Total sectors: 2930255937 (0xAEA82841)
NTFS bootsector structure:
Jump code: 0xEB 0x52 0x90
File system name: NTFS
Sector size (512): 512
Sectors per cluster: 8
Reserved sectors (0): 0
FAT copies (0): 0
Root folder items (0): 0
Total sectors (0): 0
Media ID: 0xF8
FAT size (0): 0
Sectors per track: 63
Number of heads: 255
Hidden sectors: 63
Big total sectors (0): 0
Hard disk: 0x80
Reserved: 0x00 0x0080
Big total sectors: 2930255936
MFT cluster: 786432
MFTmirr cluster: 2
MFT record size: -10
Index buffer size: 1
Serial number: 5E2E-1526-2E14-F8AB
Boot signature (0AA55h): 0xAA55
Unallocated 3-*: of size 2.5M
First sector: 2930272065 (0xAEA86741) (182401 0 1)
Last sector: 2930277167 (0xAEA87B2F) (182401 80 63)
Total sectors: 5103 (0x13EF)
Partition 1-1: file system
FS: NTFS
FSSize: 2047993 (1G)
BlockSize: 8 (4K)
BlockCount: 255999 (1G)
FreeBlockCount: 160287 (626M)
ReservedSectors: 16 (8K)
FATSize: 0 (0b)
FATCount: 0 (0b)
RootEntries: 0 (0b)
UsedRootEntries: 0 (0b)
InodeSize: 1024 (1K)
InodeCount: 256 (256K)
BytesPerInode: 0 (0b)
VolumeLabel: WINRE_DRV.......................
SerialNumber: E1 AC 5C 7A F6 5C 7A FE 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 383766752 (366M)
BadBlockCount: 0 (0b)
FreeInodeCount: 220 (220K)
FilesCount: 9
DirectoriesCount: 8
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 1792 (7M)
Options:
Partition 1-2: file system
FS: FAT32
FSSize: 532480 (260M)
BlockSize: 8 (4K)
BlockCount: 66426 (259M)
FreeBlockCount: 58851 (230M)
ReservedSectors: 34 (17K)
FATSize: 519 (260K)
FATCount: 2 (519K)
RootEntries: 0 (0b)
UsedRootEntries: 4 (128b)
InodeSize: 0 (0b)
InodeCount: 0 (0b)
BytesPerInode: 0 (0b)
VolumeLabel: SYSTEM_DRV.
SerialNumber: 5D 54 5E C0 00 00 00 00 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 30558704 (29M)
BadBlockCount: 0 (0b)
FreeInodeCount: 0 (0b)
FilesCount: 149
DirectoriesCount: 48
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 0 (0b)
Options:
Partition 1-3: file system
FS: FAT32
FSSize: 1024000 (500M)
BlockSize: 8 (4K)
BlockCount: 127746 (499M)
FreeBlockCount: 60373 (236M)
ReservedSectors: 34 (17K)
FATSize: 999 (500K)
FATCount: 2 (999K)
RootEntries: 0 (0b)
UsedRootEntries: 7 (224b)
InodeSize: 0 (0b)
InodeCount: 0 (0b)
BytesPerInode: 0 (0b)
VolumeLabel: LRS_ESP....
SerialNumber: 2B 41 60 1E 00 00 00 00 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 274785950 (262M)
BadBlockCount: 0 (0b)
FreeInodeCount: 0 (0b)
FilesCount: 158
DirectoriesCount: 204
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 0 (0b)
Options:
Partition 1-4: file system
FS: NTFS
FSSize: 432599033 (206G)
BlockSize: 8 (4K)
BlockCount: 54074879 (206G)
FreeBlockCount: 20886176 (80G)
ReservedSectors: 16 (8K)
FATSize: 0 (0b)
FATCount: 0 (0b)
RootEntries: 0 (0b)
UsedRootEntries: 0 (0b)
InodeSize: 1024 (1K)
InodeCount: 669952 (654M)
BytesPerInode: 0 (0b)
VolumeLabel: Windows8_OS.....................
SerialNumber: F1 5F 62 66 8B 62 66 E2 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 363335452673 (338G)
BadBlockCount: 0 (0b)
FreeInodeCount: 214783 (210M)
FilesCount: 375680
DirectoriesCount: 68085
HardLinkCount: 36816
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 16384 (64M)
Options:
Partition 1-5: file system
FS: NTFS
FSSize: 716793 (350M)
BlockSize: 8 (4K)
BlockCount: 89599 (350M)
FreeBlockCount: 16181 (63M)
ReservedSectors: 16 (8K)
FATSize: 0 (0b)
FATCount: 0 (0b)
RootEntries: 0 (0b)
UsedRootEntries: 0 (0b)
InodeSize: 1024 (1K)
InodeCount: 256 (256K)
BytesPerInode: 0 (0b)
VolumeLabel: ................................
SerialNumber: 3A 34 80 42 5F 80 42 68 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 296101590 (282M)
BadBlockCount: 0 (0b)
FreeInodeCount: 218 (218K)
FilesCount: 10
DirectoriesCount: 9
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 896 (3.5M)
Options:
Partition 1-6: file system
FS: NTFS
FSSize: 51212281 (24G)
BlockSize: 8 (4K)
BlockCount: 6401535 (24G)
FreeBlockCount: 3271228 (12G)
ReservedSectors: 16 (8K)
FATSize: 0 (0b)
FATCount: 0 (0b)
RootEntries: 0 (0b)
UsedRootEntries: 0 (0b)
InodeSize: 1024 (1K)
InodeCount: 768 (768K)
BytesPerInode: 0 (0b)
VolumeLabel: PBR_DRV.........................
SerialNumber: CF 3A 5A 32 66 5A 32 26 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 21340963574 (20G)
BadBlockCount: 0 (0b)
FreeInodeCount: 85 (85K)
FilesCount: 489
DirectoriesCount: 175
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 16384 (64M)
Options:
Partition 2-1: file system
FS: NTFS
FSSize: 1953516849 (932G)
BlockSize: 8 (4K)
BlockCount: 244189606 (932G)
FreeBlockCount: 173799901 (663G)
ReservedSectors: 16 (8K)
FATSize: 0 (0b)
FATCount: 0 (0b)
RootEntries: 0 (0b)
UsedRootEntries: 0 (0b)
InodeSize: 1024 (1K)
InodeCount: 978176 (955M)
BytesPerInode: 0 (0b)
VolumeLabel: DATADISK........................
SerialNumber: B8 6B 96 84 9F 96 84 EC 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 571189058809 (532G)
BadBlockCount: 0 (0b)
FreeInodeCount: 737758 (720M)
FilesCount: 229186
DirectoriesCount: 11153
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 16384 (64M)
Options:
Partition 3-5: file system
FS: NTFS
FSSize: 2930255937 (1.4T)
BlockSize: 8 (4K)
BlockCount: 366281992 (1.4T)
FreeBlockCount: 182752858 (697G)
ReservedSectors: 16 (8K)
FATSize: 0 (0b)
FATCount: 0 (0b)
RootEntries: 0 (0b)
UsedRootEntries: 0 (0b)
InodeSize: 1024 (1K)
InodeCount: 1424128 (1.4G)
BytesPerInode: 0 (0b)
VolumeLabel: ................................
SerialNumber: AB F8 14 2E 26 15 2E 5E 00 00 00 00 00 00 00 00
CheckPerformed: 1
UsefulInformation: 1496048470859 (1.4T)
BadBlockCount: 0 (0b)
FreeInodeCount: 623345 (609M)
FilesCount: 736469
DirectoriesCount: 64221
HardLinkCount: 0
SymLinkCount: 0
BlockDeviceCount: 0
CharDeviceCount: 0
SocketCount: 0
FifoCount: 0
JournalSize: 16384 (64M)
Options:
Jim, we only really needed the first part of the disk report information, not all the detailed hex data etc.
The key information from that report is that you have an UEFI system, which requires to boot in UEFI mode as you have a GPT partitioned drive.
What perhaps is still a little puzzling is why your Samsung EVO SSD is being used in IDE mode and whether you can get this to work in AHCI mode if you change this in the BIOS settings?
Here is the System Summary:
Available Physical Memory 3.95 GB
Available Virtual Memory 3.89 GB
BaseBoard Manufacturer LENOVO
BaseBoard Model Not Available
BaseBoard Name Base Board
BIOS Mode UEFI
BIOS Version/Date LENOVO ESKT22A, 12/19/2012
Boot Device \Device\HarddiskVolume2
Embedded Controller Version 255.255
Hardware Abstraction Layer Version = "10.0.14393.206"
Hyper-V - Data Execution Protection Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - VM Monitor Mode Extensions Yes
Installed Physical Memory (RAM) 8.00 GB
Locale United States
OS Manufacturer Microsoft Corporation
OS Name Microsoft Windows 10 Home
Other OS Description Not Available
Page File C:\pagefile.sys
Page File Space 1.95 GB
PCR7 Configuration Binding Not Possible
Platform Role Desktop
Processor Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz, 3001 Mhz, 4 Core(s), 4 Logical Processor(s)
Secure Boot State Off
SMBIOS Version 2.7
System Directory C:\WINDOWS\system32
System Manufacturer LENOVO
System Model 10091
System SKU LENOVO_MT_1009
System Type x64-based PC
Time Zone Central Daylight Time
Total Physical Memory 7.89 GB
Total Virtual Memory 9.84 GB
Version 10.0.14393 Build 14393
Windows Directory C:\WINDOWS
It does look like your OS is installed on a GPT disk using UEFI. So, make sure that you boot your recovery media in UEFI mode to start any restores.
PS Speed IFace Hs-Bs-Tg Model
Num NT L9NO Size FSsize Free FS Type Label ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
1- d(1) GPT 233G 132M ATA 0-0-0 Samsung SSD 850 EVO 250GB
MBR ------
GPTpri -----v
129M unallc ------
-1 ---- 1G 1G 621M NTFS 27 Windows RE H WINRE_DRV.. --c--V
-2 ---- 260M 260M 230M FAT32 EF EFI SYSTEM_DRV. --c--V
-3 ---- 500M 500M 236M FAT32 07 NTFS, HPFS LRS_ESP.... --c--V
-4 --CC 206G 206G 80G NTFS 07 NTFS, HPFS Windows8_OS --c--V
-5 ---- 350M 350M 58M NTFS 27 Windows RE H ........... --c--V
-6 ---- 24G 24G 12G NTFS 27 Windows RE H PBR_DRV.... --c--V
And your post just now also shows UEFI mode.
Here is the System Summary:
Available Physical Memory 3.95 GB
Available Virtual Memory 3.89 GB
BaseBoard Manufacturer LENOVO
BaseBoard Model Not Available
BaseBoard Name Base Board
BIOS Mode UEFI
BIOS Version/Date LENOVO ESKT22A, 12/19/2012
Boot Device \Device\HarddiskVolume2
So...
Backup OS drive as a full disk with rescue media booted in UEFI mode and keep somewhere safe.
If possible, pop out the oriignal drive and use a test drive and restore the backup to the test drive. If not possible, you have your backup to recover from should things go south, but not having ot do this on the original would be ideal if possible.
Boot to the OS and go through the process of prepping the system from IDE to SATA, shutdown completely, switch bios SATA mode from IDE to AHCI. Boot up the OS. It may require another reboot or 2, but once it boots normally, you're good.
Take a new backup of the OS drive as a full disk with rescue media booted in UEFI mode and keep somewhere safe.
Restore this image to the SSD in the new system. Make sure bios has the correct drive listed as the boot priority and that the SATA mode is AHCI. Boot the drive and see what happens. It might just work with Windows 10. If not, then you'd boot UR in UEFI mode on the new system, run it to generalize the drivers and hopefully the OS boots on the new hardware. You'd then go through the process of installing drivers in Windows as needed.
Licensing assumes you already activated Windows 10 OEM on the new hardware before all this at least once, or it's not likely that the Windows license will activate from the copied OS.
If possible, pop out the oriignal drive and use a test drive and restore the backup to the test drive. If not possible, you have your backup to recover from should things go south, but not having ot do this on the original would be ideal if possible.
I assume you mean to do this on my current (the original) system. Why would I do this? Is it just to prove the Acronis recovery works? I think I remember reading the partition one restores to must be the same size as the original partition. That would not be true of the spare drive I have to do this with.
Boot to the OS and go through the process of prepping the system from IDE to SATA, shutdown completely, switch bios SATA mode from IDE to AHCI. Boot up the OS. It may require another reboot or 2, but once it boots normally, you're good.
As I mentioned earlier, the time I tried to change the BIOS from IDE to SATA everything went crazy. It presented several different failure messages. One of them wanted me to reinstall windows. These messages seemed to be generated by then motherboard/BIOS but I couldn't be sure of that -- I judged that partly because the messages began coming so quickly after start, and it quit giving the startup beep and partly because the hard drive light never came on. Then the system began rebooting over and over. I thought I had lost my entire system. Finally, after it had done this for a while it gave a option that let me reboot. I immediately grabbed the BIOS and changed it back to IDE and everything began working properly.
Jim, these actions are being advised to you in order to try to help you succeed in doing what you are asking about but if you do not wish to follow the advice that is your choice.
The suggestions from Rob above are trying to help you protect your current Lenovo system while proving that it is possible to switch your SATA mode over from IDE to AHCI.
See webpage: How to Change SATA Hard Disk Mode from IDE to AHCI / RAID in BIOS after Installing Windows? and / or webpage: How to: Change SATA Modes After Windows Installation which both offer similar advice showing that this is possible to do. The next steps are down to you to make or not.
Jim, ultimately it is all up to you. You can follow advice and hopefully have success with minimal risk and options to revert back, or you can go about it however you see fit, or do nothing at all and build from scratch.
Best of luck in whatever you do.
The Registry approach seems OK to me. It's a little tricky/iffy to catch the BIOS on bootup. If I miss it with everything crash? But, I can turn off the machine and start again?
Well, maybe not. I don't have an HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci entry in my Registry. See screen capture. Are we sure this is for Win10? It didn't say what version on the page. I do have the pciide entry and it's already set to 0.
Ive used both of these methods on win10. Microsoft actually used to have a fixit toll for this, but pulled it for some reason.
http://www.tomshardware.com/answers/id-2795928/switch-ide-ahci-windows…
http://triplescomputers.com/blog/uncategorized/solution-switch-windows-…
Okay, I've gone into Safe Mode and recovered successfully so I plan to try triplescomputers method.
When I do it for real I'll be restoring to the same drive my system is on now. But, to test restore on another, much larger, drive I didn't get an answer. Do I have to create a set of partitions the same sizes as the current ones or does Acronis Restore do that automatically?
Jim, do a disk level restore then you don't need to have to set partition sizes individually etc.
See post: 128057: [Tutorial] How to recover an entire disk backup which deals with this specific subject.
Many thanks to both of you. If it works I could never have done it without your help. My computer should be here late this week. I'll let you know how it all turns out.
Thanks Jim, hope the new computer arrives safe and all goes well with the transition. Please do let us know the outcome.
It turns out I have another question.
See attached. I don't like surprises so I was walking up to the edge of doing a restore just to see how it would be, and got the attached warning.
Jim, the warning message indicates that you have not booted the Acronis Rescue Media in the correct BIOS mode, i.e. your system is UEFI with GPT and the Rescue Media must also be started in this same UEFI mode but has been started in Legacy mode.
See post: https://forum.acronis.com/forum/119666#comment-365312 where the same issue was shown.
It is in the mode I always boot in. Does this mean, after the restore I should change it back before booting into Windows?
Jim, from the information you provided in the earlier posts, your Windows OS boots in UEFI mode, but the error message you are seeing is coming because when you are booting the Rescue Media, this is being booted in Legacy mode - this may be because of the BIOS setting shown in your earlier screen capture where you have it set to Legacy first.
Do you think it is safe to change that setting from Auto to UEFI?
Jim, yes, it should be safe to set the BIOS boot setting to UEFI instead of Auto, or you could select UEFI First if this is available.
If you wonder why I haven't been back, my computer quit booting a day or or so after I went into Safe Mode. I'm posting this from my wife's computer which I find difficult to use. Here's a descriiption of the failure I posed on a ccomputer building forum:
A short while ago my 4 year old Lenovo computer started delaying for up to 5 minutes before starting a reboot. After that, it would boot normally and I could leave windows running for a day. But when I would reboot, it would take the same five minutes again. Now it won’t boot at all. The power light is on and the power supply checks good. What could be causing this behavior?
I wouldn't expect anyone here to have any ideas about the cause as I got no replies on the computer forum.
I now have two more questons:
- Can I install Acronis on my wife's computer long enough to make the Universal Restore boot disk?
- If so, and my new motherboard permists, should I install windows 10 as IDE, do the universal restore and then try the trick to convert?
Make that three questions.
Will a universal restore disk made on a Win7 computer work on Win10?
If you wonder why I haven't been back, my computer quit booting a day or or so after I went into Safe Mode. I'm posting this from my wife's computer which I find difficult to use. Here's a descriiption of the failure I posed on a ccomputer building forum:
A short while ago my 4 year old Lenovo computer started delaying for up to 5 minutes before starting a reboot. After that, it would boot normally and I could leave windows running for a day. But when I would reboot, it would take the same five minutes again. Now it won’t boot at all. The power light is on and the power supply checks good. What could be causing this behavior?
I wouldn't expect anyone here to have any ideas about the cause as I got no replies on the computer forum.
Jim, you say the power supply checks good - how have you reached this conclusion? Is this a desktop or a laptop computer?
In this type of situation I would suggest reducing the computer down to a minimal configuration, i.e. remove all devices / cards / peripherals that are not essential. If you have more than one memory module installed, try removing one of these at a time and try booting. Try booting from a CD or USB stick such as the Acronis Rescue Media - does that work correctly?
I now have more questons:
- Can I install Acronis on my wife's computer long enough to make the Universal Restore boot disk?
- If so, and my new motherboard permists, should I install windows 10 as IDE, do the universal restore and then try the trick to convert?
- Will a universal restore disk made on a Win7 computer work on Win10?
- Yes, you can and depending on how many licenses you have, you may be challenged about exceeding the number of activations. See KB 58554: Acronis True Image 2017: "You've exceeded the maximum number of activations for this serial number" for how to handle this.
- Cannot say as do not know if your new motherboard will allow the SATA mode as IDE.
- Yes it should, especially if you are creating the standard, linux version as the host OS would make no difference. If you are creating the Windows PE version of the media, then you should install the Windows 10 ADK on the Windows 7 computer. The only issue that may arise here is if your Windows 7 computer is 32-bit and your target computer is 64-bit, as it is not possible for a 32-bit system to create the 64-bit media.
Jim, you say the power supply checks good - how have you reached this conclusion? Is this a desktop or a laptop computer?
I have an ANTEC power supply checker. Desktop.
Try booting from a CD or USB stick such as the Acronis Rescue Media - does that work correctly?
I've not gone a far as you suggest, but I have removed all external peripherals except mouse and keyboard. But,as of now it simply does nothing. When I say will not boot, I mean the boot sequence does not start. So it will not reach the point of booting from a CD. I will try what you suggest, removing cards and memory. And, I suppose I can remove mouse and keyboard to see if it can start then.
I removed everything removable including the hard drives, but since I had also removed the video connector I had to depend on the post beep, which I didn't get. But I've had motherboards with no speaker and depend on the external speakers. So I had to reconnect the monitor. If the monitor is the problem and there's no speaker I have no way to tell.
Jim, thanks for the further information, sorry that the results of reducing the system to a minimal configuration has not helped to identify the issue other than the prospect that the motherboard itself (or CPU) is the root failure item.
If you have a spare / different PSU you could try connecting, even if just sitting outside the case, it may be worth it. I have never used a PSU checker but have experienced enough failed PSU's to keep a spare in my cupboard that I can swap in quickly when dealing with this type of problem to eliminate it (or not).
This has become an acidemic discussion since I have neither an extra CPU or motherboard. But, I assume, because it runs perfectly when I finally boots, it can't be the processor. My money is on the motherboard.
Jim, sorry to just be getting back - so it does eventually boot, but just slow? Or is it a complete no-go with booting right now?
I've had weird bios issues with my Gigabyte Z170X Gaming 3 bios. In a few different occassions, it just seemed to ignore some of the changes. I've resorted to reflashing the latest firmware to force everything back to default and then all is well again. Might work for you as well, but hopefully you don't have to do the same.
Did you verify the bootorder in the bios is showing the main hard drive in UEFI mode (usually says windows bootmanager in the name for UEFI mode) so that it's not trying to boot to some other drive first before it finally settles on the correct drive?