How to clone/migrate O/S system disk sata ssd over too a new NVME M2 SSD without data loss
Dave,
Sorry, I stand corrected. I had thought there was an operational or usage guide posted for the MVP tool. I cannot seem to find it now.
The tool is easy to use so just follow what it asks and you should be fine. If you fail somewhere just start again.
That's it, I had forgotten it got turned into a KB article! Lol
************************************************* 07-12-2018_22.11.48 MVP Tool - Acronis WinPE Rescue Media Builder v.18.2 ************************************************* ------------------ SYSTEM INFORMATION: ------------------ PC NAME: ASUS-PC BIOS UUID: 15BDEF20-D7FC-11DD-BD74-305A3A06E421 --------------- OS INFORMATION: --------------- NAME: Microsoft Windows 7 Ultimate VERSION: 6.1.7601 BUILD: 7601 ARCH: 64-bit DIRECTORY: C:\Windows LANGUAGE: en-US OS UUID: f35d3739-3fac-4131-8d98-6fab0e36e685 ------------------- ACRONIS INFORMATION: ------------------- WINDOWS SNAPMAN VERSION: 4.7.0.2599 ATIH VERSION: 2019 ATIH BUILD: 23.4.1.14690 SD BUILD: NotFound UR VERSION: NotFound DD VERSION: NotFound DD BUILD: NotFound Acronis Revive VERSION: NotFound Acronis Revive BUILD: NotFound -------------- VARIABLE PATHS: -------------- SCRIPT SOURCE: E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182 ATIH PATH: C:\Program Files (x86)\Acronis\TrueImageHome\WinPE SD PATH: NotFound UR PATH: NotFound DD12 PATH: NotFound Acronis Revive PATH: NotFound ADK PATH: E:\ADK\Assessment and Deployment Kit\Windows Preinstallation Environment ---------------- ADK INFORMATION: ---------------- Installed: 10.0.17763 WINRE64: NotFound WINRE86: NotFound @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ MVP ATIPeBuilder LOG DETAILS: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 07-12-2018 22.11.48 You chose [2.] "64-bit Media Builder" - USER selected. 07-12-2018 22.11.48 Skipping network share mapping - USER selected. 07-12-2018 22.11.48 Mounting amd64 winpe.wim. 07-12-2018 22.11.48 The default OS language is English - skipping language options. 07-12-2018 22.11.48 True Image Found. Adding It. 07-12-2018 22.11.48 True Image snapman Version: 4.7.0.2599 07-12-2018 22.11.48 Snap Deploy Not Found. Skipping It. 07-12-2018 22.11.48 Universal Restore Not Found. Skipping It. 07-12-2018 22.11.48 Disk Director 12 Not Found. Skipping It. 07-12-2018 22.11.48 Acronis Revive 2017 Not Found. Skipping It. 07-12-2018 22.11.48 Adding in extra goodies. ---------------------------------------------------------------------------------------- 07-12-2018 22.11.48 START injecting CUSTOM 64-bit drivers - USER selected. ---------------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.1 Searching for driver packages to install... Found 3 driver package(s) to install. Installing 1 of 3 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\IRST\iaAHCIC.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. Installing 2 of 3 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\IRST\iaStorAC.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. Installing 3 of 3 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\NIC\Killer e2200 Gigabit Ethernet Controller\oem59.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. The operation completed successfully. ---------------------------------------------------------------------------------------- 07-12-2018 22.11.48 END injecting CUSTOM 64-bit drivers. ---------------------------------------------------------------------------------------- 07-12-2018 22.11.48 Skipping MSiScsi Support Packages - USER selected. 07-12-2018 22.11.48 Skipping Bitlocker Support Packages - USER selected. 07-12-2018 22.11.48 Prompt for any key at boot - USER selected. 07-12-2018 22.11.48 Skipping WinPE screen resolution - USER selected. 07-12-2018 22.11.48 Saving changes to amd64 winpe.wim file. 07-12-2018 22.11.48 Creating Acronis_MVP_PEMedia_amd64.iso. 07-12-2018 22.11.48 Acronis_MVP_PEMedia_amd64.iso is located in "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO" 07-12-2018 22.11.48 Creating Acronis_MVP_PEMedia_amd64.wim. 07-12-2018 22.11.48 Acronis_MVP_PEMedia_amd64.wim is located in "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO\Wim". 07-12-2018 22.11.48 Creating USB flash drive - USER Selected. 07-12-2018 22.11.48 USB flash drive letter is [G - USER Selected.
Is the log file, i couldn't see how to point to the up to date RST & Samsung nvme drivers , If i try adding the drivers within acronisit doesn't see the .inf files, but the samsung driver doesn't have .inf files when extracted
Update: I can't add the Samsung NVME driver From the location that i extracted it to, because it contains no .INF file types but if i browse to my win 7 installation program files there are 1.inf 2.sys and 1.cat files are these all that are needed, i have not got the Intel RST drivers added to the Acronis TI
HERE are the drivers that i have been able to add is this correct or have i missed something
Yes, add all of those drivers. Those are the IRST (Intel Rapid Storage Technology) which includes the Intel versions and the last one appears to be the Samsung specific driver. IRST is all you should need, but not going to hurt to add the Samsung ones.
As for the MVP tool. It looks like you created a bootable UsB as the G: drive on your system. If you're looking for the .iso or the .wim (a .wim is the windows image that boots in WinPE, but needs to be put on a bootable disk - which should already have been copied to your G: drive).
Those were created in the MVP tool folder:
E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO" "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO\Wim".
The IRST drivers already exist in the MVP tool and when you select custom injection, will add those for you. If you want to remove them, or add any of your own custom drivers, put them in the folder before you run the tool and select Yes to inject custom drivers. The custom drivers folder in your instance is located at:
E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64
The bootable media that i created yesterday on my 16gb pen drive has partitioned it, how to i removed or extend the partion again as it's showing as 418mb, when it's 16 gb
I'm not sure I follow how it got partitioned - using the MVP tool? Or did you do something else? Thumb drives typically can only display one active parition in Windows (although can have multiple and can be seen with Linux / Unix tools).
I used to use minitool paritionwizard free to format and/or partition thumb drives and SSD's. Back in 9.1 you could do it without having to install the software at all. Since 9.2 and later, if using the free version, you have to install it on your PC and can do this from the application. Still a great tool, but I use it so much I bought it. I prefer it over most other parition tools, although I own 3-4 of them since they all had lifetime licenses and I wanted to test them out.
Basically, if you want the full pen drive back in Windows, you need to do a long format of the drive. Minitool is great for this. However, if you want to stick to free, then you can use Windows command line via the Diskpart command. Be careful, it's powerful and won't always prompt you with an "are you sure" option so make sure you format the correct drive. This says for Windows 10, but it's the same in Windows 7.
https://www.intowindows.com/how-to-format-usb-flash-drive-via-command-p…
------------------------------------
FYI, I think you can forget the samsung drivers directly in the WinPE. Came across this forum and Samsung says they are not designed for this - only for optimization within the OS. So, the IRST drivers from Microsoft are what you want to inject into the WinPE and/or have on hand if doing a Windows 7 new install onto a PCIE NVME drive.
https://us.community.samsung.com/t5/Memory-Storage/Samsung-NVMe-SSD-960…
I used the acronis linux based recovery tool I just formatted it so i could add this new reccoverywin pe based image with the drivers, As for adding these drivers am i correct in adding them to the folder within the MVP tool where it indicates to put them, before i run the tool? those irst sdrivers pre added i have removed as the intel rst for my board is a difgferent version i have replaced with the correct drivers is this correct or do i need both sets ?
Dave,
The 18.2 version of the MVP tool which is what you are running has Intel IRST driver version series 15.20.0.1020. These will work fine for you to perform your restore with. No need to update these here since you have a 15.2 series driver installed and working on your system now, you know that works.
Selecting Yes when prompted as shown in your screenshot will inject the drivers listed above.
Did you find the Win 7 x64 SP 1 hotfix as well? It seems MS removed it..
https://support.microsoft.com/en-us/help/2990941/update-to-add-native-d…
links to this which says no longer available
https://support.microsoft.com/en-us/help/4343220/this-hotfix-is-no-long…
If that's the case, this is what I would do...
1. Remove the Samsung PCIE NVME driver from Windows 7 completely.
2. Reboot
3. Verify if the PCIE NVME drive shows up in Windows disk manager or not (assuming not, but may if you have the IRST drivers installed)
4) If not, install the IRST drivers for Windows 7 x64 into the OS from Intel:
https://downloadcenter.intel.com/download/27400/Intel-Rapid-Storage-Tec…
From there, get the setuprst.exe and install it in Windows
5) Reboot.
6) Verify that the Windows OS can see the NVME PCIE drive in Windows diskmanger (assuming yes now)
7) Shutdown, remove PCIE NVME drive
8) boot Windows OS. Take full disk backup of the drive with Acronis
9) Shutdown. Remove original OS drive. Insert PCI NVME drive.
10) Boot to system bios and ensure bios sees drive
11) Shutdown and boot to Acronis rescue media
12) Restore full disk backup to the PCIE NVME drive
13) shutdown the system
14) boot to bios and ensure it sees the PCI NVME drive again (this may allow the motherboard to detect the OS on the drive and set it as the boot drive automatically)
15) Try to boot Windows
Hopefully it "just works" now. If not, power down and try to boot into safe mode (may need to check user manual how to do that on your system (F8 on most systems).
If it boots into safe mode successfully, you're probably golden now - the OS may have been "locked" and this will unlock it on the disk again.
Feel free to install the Samsung driver if you want now.
Ok, i have managed to get the flash drive back to it's original state and formatted to fat32
As for the MS patches they pulled both from their normal site ,but the later patch is still available from the that other MS location for finding patches its name escapes me, but it's where those who only download the security only patches to avoid GWX (Windows 10 )and telemetry, in their roll-up patches I installed the KB 4343220 Patch
I have already made a full system disk backup with the Samsung driver installed, Also re Samsung support, they claim that their data migration tool will migrate the os from an SSD to nvme, and the facts are it don't work, because their crap tool hangs at 99% verifying the clone whilst giving the impression that it's doing something at 7mb/s when it had actually stopped doing anything over 2 hours before, So i personally wouldn't take whatever they say seriously, Without the driver the drive may not be able to be written to or be unbootable
BTW my Intel driver version is 15.8.2
Rob,
The OP has installed the MS hotfix. He has Intel family series 15.2 drivers installed as well. He has the Samsung NVMe driver installed. We know that his Legacy MBR SSD boots fine with those all in place. What the goal is now is to use TI booted from the MVP WinPE media to restore/convert a backup image of the above to an installed NVMe drive.
Dave, if you will just run the MVP tool again to your flash drive, answer yes when asked to inject custom drivers, and let the tool complete the build you should be all set here.
So no need to use the ATI software to create, add drivers ect to this bootable win pe recovery media then?
That is correct. Remember, you are only adding support for WinPE itself at this stage. It will have no impact on your Win 7 install what so ever.
After you have your new NVMe up and running you can then update the Intel driver in Device Manager at that time if you choose to do so.
Bobbo_3C0X1 wrote:
Just got this message, or been alretedto it, reading this indicates that they are refering to installing WIN7 not restoring a working image
Ok, Just re ran the MVP tool it has created a win and iso file but didn't write any data to the flash drive, i entered the correct drive letter G:> in that format which i read it to be requiring lol, G: no > sorted written to the usb pen drive,
Now to clean PC install nvme, remove/disconnect Legacy os ssd, and the other data HDD, leaving just the source with the backup on it and the blanc Nvme is this correct or do i still need acronis TI for anything else?
Drive letter should be G:
nothing else
Looking at the logs the MVP tool has created there's no mention of the Samsung drivers only the intel drivers, should there be a reference to them in the log? scrub that i was looking at the wrong log, lol it's there, and it didn't claim the whole space on the flash drive unlike that linuxbase ATI recovery tool
Nope, the MVP tool only includes the IRST drivers - that's all you need for the WinPE to detect the PCI NVME drive. Purpose is so the WinPE can see the drive so you can point your backup .tib to restore to it. It has no impact on the existing OS or anything like that. So, as long as it sees your hardware and can use it, mission accomplished for the rescue media build.
So sounds like you have the WinPE media built and can now boot to it and perform your recovery to your NVMe correct?
It says it has written it to the usbdrive and there are many files on it now in a folder type structure
Yes, looks good! Congrats!
Now you just need to boot to it in UEFI mode. In your bios enable UEFI in the Boot tab, disable Secure Boot if it is enabled. In the Boot Order list make sure that your flash drive with UEFI in the preceding the name of the drive is first in the list. Set the SATA Mode to RAID, Save the new configuration and Exit the bios. The machine should boot into the WinPE flash drive and the Acronis True Image app should start and display the Home screen.
Ok installed the 970 evo nvme disk , I set the bios to boot in uefi mode, secure boot was greyed out and enabled ,unable to change that ??? changed the PCH storage to raid,(tried both ahci and raid options ) And booted from the usb flash drive, which gets as far as a blue MVP forum loading screen, and then nothing, pressed every F key, ESC ,enter nothing no responce what so ever?
Dave,
Can you post the MVP tool log file or can you verify that True Image was successfully copied to the flash drive?
I am going to research how to setup a PCIe based drive on your mobo to see what settings are necessary to get it working. It will take me awhile so please be patient.
Where on the usb imigage would be, ie file name just that i didn't re connect my HHD where the log from the tool is stored but looking at the folders on the flash drive i don't see any called true image
It's claims to of added TI but it ain't written it to the flash drive ?
------------------- ACRONIS INFORMATION: ------------------- WINDOWS SNAPMAN VERSION: 4.7.0.2599 ATIH VERSION: 2019 ATIH BUILD: 23.4.1.14690 SD BUILD: NotFound UR VERSION: NotFound DD VERSION: NotFound DD BUILD: NotFound Acronis Revive VERSION: NotFound Acronis Revive BUILD: NotFound -------------- VARIABLE PATHS: -------------- SCRIPT SOURCE: E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182 ATIH PATH: C:\Program Files (x86)\Acronis\TrueImageHome\WinPE SD PATH: NotFound UR PATH: NotFound DD12 PATH: NotFound Acronis Revive PATH: NotFound ADK PATH: E:\ADK\Assessment and Deployment Kit\Windows Preinstallation Environment ---------------- ADK INFORMATION: ---------------- Installed: 10.0.17763 WINRE64: NotFound WINRE86: NotFound @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ MVP ATIPeBuilder LOG DETAILS: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 08-12-2018 00.40.01 You chose [2.] "64-bit Media Builder" - USER selected. 08-12-2018 00.40.01 Skipping network share mapping - USER selected. 08-12-2018 00.40.01 Mounting amd64 winpe.wim. 08-12-2018 00.40.01 The default OS language is English - skipping language options. 08-12-2018 00.40.01 True Image Found. Adding It. 08-12-2018 00.40.01 True Image snapman Version: 4.7.0.2599 08-12-2018 00.40.01 Snap Deploy Not Found. Skipping It. 08-12-2018 00.40.01 Universal Restore Not Found. Skipping It. 08-12-2018 00.40.01 Disk Director 12 Not Found. Skipping It. 08-12-2018 00.40.01 Acronis Revive 2017 Not Found. Skipping It. 08-12-2018 00.40.01 Adding in extra goodies. ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 START injecting CUSTOM 64-bit drivers - USER selected.
************************************************* 08-12-2018_00.40.01 MVP Tool - Acronis WinPE Rescue Media Builder v.18.2 ************************************************* ------------------ SYSTEM INFORMATION: ------------------ PC NAME: ASUS-PC BIOS UUID: 15BDEF20-D7FC-11DD-BD74-305A3A06E421 --------------- OS INFORMATION: --------------- NAME: Microsoft Windows 7 Ultimate VERSION: 6.1.7601 BUILD: 7601 ARCH: 64-bit DIRECTORY: C:\Windows LANGUAGE: en-US OS UUID: f35d3739-3fac-4131-8d98-6fab0e36e685 ------------------- ACRONIS INFORMATION: ------------------- WINDOWS SNAPMAN VERSION: 4.7.0.2599 ATIH VERSION: 2019 ATIH BUILD: 23.4.1.14690 SD BUILD: NotFound UR VERSION: NotFound DD VERSION: NotFound DD BUILD: NotFound Acronis Revive VERSION: NotFound Acronis Revive BUILD: NotFound -------------- VARIABLE PATHS: -------------- SCRIPT SOURCE: E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182 ATIH PATH: C:\Program Files (x86)\Acronis\TrueImageHome\WinPE SD PATH: NotFound UR PATH: NotFound DD12 PATH: NotFound Acronis Revive PATH: NotFound ADK PATH: E:\ADK\Assessment and Deployment Kit\Windows Preinstallation Environment ---------------- ADK INFORMATION: ---------------- Installed: 10.0.17763 WINRE64: NotFound WINRE86: NotFound @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ MVP ATIPeBuilder LOG DETAILS: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 08-12-2018 00.40.01 You chose [2.] "64-bit Media Builder" - USER selected. 08-12-2018 00.40.01 Skipping network share mapping - USER selected. 08-12-2018 00.40.01 Mounting amd64 winpe.wim. 08-12-2018 00.40.01 The default OS language is English - skipping language options. 08-12-2018 00.40.01 True Image Found. Adding It. 08-12-2018 00.40.01 True Image snapman Version: 4.7.0.2599 08-12-2018 00.40.01 Snap Deploy Not Found. Skipping It. 08-12-2018 00.40.01 Universal Restore Not Found. Skipping It. 08-12-2018 00.40.01 Disk Director 12 Not Found. Skipping It. 08-12-2018 00.40.01 Acronis Revive 2017 Not Found. Skipping It. 08-12-2018 00.40.01 Adding in extra goodies. ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 START injecting CUSTOM 64-bit drivers - USER selected. ---------------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.1 Searching for driver packages to install... Found 4 driver package(s) to install. Installing 1 of 4 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\970_Win7_64\secnvme.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. Installing 2 of 4 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\IRST\iaAHCIC.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. Installing 3 of 4 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\IRST\iaStorAC.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. Installing 4 of 4 - E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\Drivers_Custom\x64\NIC\Killer e2200 Gigabit Ethernet Controller\oem59.inf: INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match. The driver package was successfully installed. The operation completed successfully. ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 END injecting CUSTOM 64-bit drivers. ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 Skipping MSiScsi Support Packages - USER selected. 08-12-2018 00.40.01 Skipping Bitlocker Support Packages - USER selected. 08-12-2018 00.40.01 Prompt for any key at boot - USER selected. ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 START Setting WinPE screen resolution 1920 x 1080 - USER selected. ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 END Setting WinPE screen resolution 1920 x 1080. ---------------------------------------------------------------------------------------- 08-12-2018 00.40.01 Saving changes to amd64 winpe.wim file. 08-12-2018 00.40.01 Creating Acronis_MVP_PEMedia_amd64.iso. 08-12-2018 00.40.01 Acronis_MVP_PEMedia_amd64.iso is located in "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO" 08-12-2018 00.40.01 Creating Acronis_MVP_PEMedia_amd64.wim. 08-12-2018 00.40.01 Acronis_MVP_PEMedia_amd64.wim is located in "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO\Wim". 08-12-2018 00.40.01 Creating USB flash drive - USER Selected. 08-12-2018 00.40.01 USB flash drive letter is [G:] - USER Selected. 08-12-2018 00.40.01 Skipping CD/DVD burning - USER Selected. 08-12-2018 00.40.01 Cleaning up now. 08-12-2018 00.40.01 FINISHED.
Full log if you need it, the data written to the USB flash drive is around 382mb in size
Dave,
Please confirm that you did in fact install the MS hotfixes. These would be both KB2990941 and KB3087873 ?
In researching this both of these hot fixes are required for the MS fixes to work.
Enchantech wrote:Dave,
Please confirm that you did in fact install the MS hotfixes. These would be both KB2990941 and KB3087873 ?
In researching this both of these hot fixes are required for the MS fixes to work.
Only the hotfix that fixed the 1st hotfix that MS has pulled from it's server that being the KB 308...
But i have just found it via another 3rd party source http://thehotfixshare.net/board/index.php?autocom=downloads&showfile=20015
Sick of this modderationthat doesn't work, apart from to make communications harder and more confusing
I found a copy of the older pulled hotfix , http://thehotfixshare.net/board/index.php?autocom=downloads&showfile=20015
The other begining 308 is already installed
can you please explain how only having one of the 2 hotfixes installed to my current working win7 installation and, a back up / image of that, is preventing progress at the stage where i'm at please,
IMO i can't it be the reason why i'm not able to even start the recovery process because the mvp tool is just win PE, no connection to my o/s or image until i was to get to a stage of actually loading said image onto the nvme is this correct? if it is then not having that other hotfix can't be the reason for it hanging at the first screen and not offering any menu options ect ,whilst i do except that if i was able to recover the image it may not work correctly or at all so i'm not saying you are wrong just that i cannot see how this is why it failed to cross the start line
But for the record that 1st hotfix is now also installed i take it i shall have to create another full disk backup, and delete the current backup ?
Update , i have created a new full system backup with both hotfixes installed,Is there any point in building a new PE recovery bootable usb image?
Bobbo_3C0X1 wrote:Did you find the Win 7 x64 SP 1 hotfix as well? It seems MS removed it..
https://support.microsoft.com/en-us/help/2990941/update-to-add-native-d…
links to this which says no longer available
https://support.microsoft.com/en-us/help/4343220/this-hotfix-is-no-long…
If that's the case, this is what I would do...
1. Remove the Samsung PCIE NVME driver from Windows 7 completely.
2. Reboot
Yes i got the kb2990941 from a 3rd party site and it now installed so both are now installed
3. Verify if the PCIE NVME drive shows up in Windows disk manager or not (assuming not, but may if you have the IRST drivers installed)
I have RST installed already
4) If not, install the IRST drivers for Windows 7 x64 into the OS from Intel:
https://downloadcenter.intel.com/download/27400/Intel-Rapid-Storage-Tec…
From there, get the setuprst.exe and install it in Windows
5) Reboot.
6) Verify that the Windows OS can see the NVME PCIE drive in Windows diskmanger (assuming yes now)
The NVME SSD does not install correctly without the samsang driver, it is not useable without it
7) Shutdown, remove PCIE NVME drive Can you please explain why i should have to remove it again
8) boot Windows OS. Take full disk backup of the drive with Acronis
9) Shutdown. Remove original OS drive. Insert PCI NVME drive.
10) Boot to system bios and ensure bios sees drive
11) Shutdown and boot to Acronis rescue media
12) Restore full disk backup to the PCIE NVME drive
13) shutdown the system
14) boot to bios and ensure it sees the PCI NVME drive again (this may allow the motherboard to detect the OS on the drive and set it as the boot drive automatically)
15) Try to boot Windows
Hopefully it "just works" now. If not, power down and try to boot into safe mode (may need to check user manual how to do that on your system (F8 on most systems).
If it boots into safe mode successfully, you're probably golden now - the OS may have been "locked" and this will unlock it on the disk again.
Feel free to install the Samsung driver if you want now.
But why isn't the MPV Tool working , it hasn't got past the fist screen, so the the backupwith driver on it hasn't come in to play,as far as i can see, now you are suggesting i use ati only ?
Dave,
Ok, we MVP's here are trying to do two things at once. First, we are trying to help you fix your problem and enjoy your new blazing fast NVMe drive. Second, we are attempting to provide driver support for NVMe and NVMe RAID in the MVP tool for Windows 7 X64 and X32 users.
In my research I found just this morning that having the MS hot fixes and the Samsung driver installed will not work together when it comes to trying to install Win 7. The reason for this is a conflict between drivers that prohibits the detection of an NVMe drive. So at this point that leaves you in perfect position to complete your task and get your system up and running. So long story short here I needed to know if you had both hotfixes and the Samsung drivers installed in your Win 7 installation to help in moving our MVP tool support forward. Thank you for your help in that.
Now as to why the media you built is not finishing loading. It is very simple. During the build process you are selecting a video resolution of 1920 by 1080. This is causing the loading of your video driver to fail and so WinPE is hung at that point. Please rebuild the WinPE media again and when asked for video resolution select the default option A. This should fix the issue you have and allow WinPE to continue loading and the True Image app to load and display on screen.
Again, thanks for your help.
Ok, thanks, again, So just so we are on the same page on all this
I now have both hotfixes installed and the Samsung driver, is this ok or not? as I'm seeing conflicting info and this is only leading to confusion
So i deleted the 1st backup, and have made a new one with both hotfixes and the Samsung nvme driver, again is this ok? I will create another MVP tool build, with the default resolution
The reason for this is a conflict between drivers that prohibits the detection of an NVMe drive. So at this point that leaves you in perfect position to complete your task and get your system up and running. So long story short here I needed to know if you had both hotfixes and the Samsung drivers installed in your Win 7 installation to help in moving our MVP tool support forward. Thank you for your help in that.
Also BIOS config, CSM i believe would need to be disabled in order to disable secure boot, but if it is greyed out it is supposed to be disabled regardless of what the greyed out option is, i know that secure boot will not work with win7, also i wasn't seeing anything relating to UEFI boot manager in the bios for the usb flash drive
08-12-2018 21.59.32 Skipping MSiScsi Support Packages - USER selected. 08-12-2018 21.59.32 Skipping Bitlocker Support Packages - USER selected. 08-12-2018 21.59.32 Prompt for any key at boot - USER selected. 08-12-2018 21.59.32 Skipping WinPE screen resolution - USER selected. 08-12-2018 21.59.32 Saving changes to amd64 winpe.wim file. 08-12-2018 21.59.32 Creating Acronis_MVP_PEMedia_amd64.iso. 08-12-2018 21.59.32 Acronis_MVP_PEMedia_amd64.iso is located in "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO" 08-12-2018 21.59.32 Creating Acronis_MVP_PEMedia_amd64.wim. 08-12-2018 21.59.32 Acronis_MVP_PEMedia_amd64.wim is located in "E:\INSTALLERS\ATI_PE_BUILDER-20181206T213444Z-001\ATI_PE_BUILDER\Advanced\MVP_ATIPEBuilder_v182_signed\MVP_ATIPEBuilder_v182\ISO\Wim". 08-12-2018 21.59.32 Creating USB flash drive - USER Selected. 08-12-2018 21.59.32 USB flash drive letter is [G:] - USER Selected. 08-12-2018 21.59.32 Skipping CD/DVD burning - USER Selected. 08-12-2018 21.59.32 Cleaning up now. 08-12-2018 21.59.32 FINISHED.
This time i used the default screen resolution and still the same thing, I also tried raid, instead of AHCI in the satapart of the pch storage part of the bios as well as the m.2 raid mode , set bios to boot in uefi only set the oprom to uefi only ,from uefi and legacy boot , none of it made one bit of difference, still hangs at the start screen , and i'm getting sick of un plugging /plugging in my o/s ssd
Can any one confirm if CSM mode should be disabled or not
Dave,
I would remove the Samsung Drivers since you have the Microsoft drivers and hotfix applied. I've also ready that there are conflicts in Windows 7 (I have both in Windows 10 without issue though). This could still be why you're seeing a bad driver error after restore.
CSM is only needed when you want the option to legacy (MBR boot). It shouldn't hurt to have it enabled or disabled though, as long as you're still are picking to boot the recovery drive in UEFI mode.
Also, I can't tell if you are injecting the custom drivers and/or the system drivers since the log is cut off. Just want to make sure you are selecting to use the custom driver option with just the default drivers in the folder.
And to be sure, you're using the 18.2 builder or something earlier?
Dave,
First, we know that the MS hotfixes installed on your Win 7 working system work to detect the NVMe drive correct?
So from what I have read if you install the Samsung drivers with the hotfixes applied this will not work because of a conflict between the drivers. This is an old post on the Dell support site and was true for Samsung driver 1.4.7.6. We are several versions beyond that now in drivers. So this may not apply anymore. I am pasting that part of the Dell post below for your convenience.
Update NVMe drives with Microsoft HotFix and remove Samsung Drivers
Samsung Drivers (Ver: 1.4.7.6) cannot be used at the same time as the Microsoft Windows 7 SP1 or Windows Server 2008 R2 SP1 HotFixes (KB2990941, KB3087873). If you have a Samsung-manufactured NVMe SSD as boot drive with Samsung Drivers and you want to install the Microsoft NVMe HotFixes you must reimage your operating system.
Because of this post I am unsure if having the Samsung driver installed along with the MS hotfixes in your backup image and writing that image to your NVMe drive to make it the boot device will work as this indicates that a conflict exists between the two.
As for the WinPE, having the Samsung driver installed in WinPE will allow WinPE to detect and work with the NVMe drive which is what we want in that scenario. We have not and are not applying the MS hotfixes to the WinPE environment so the Samsung drivers are necessary for WinPE.
So at this point I think you have 3 choices.
- Leave the MS hotfixes installed and uninstall the Samsung driver from your current Win 7. Then create a new backup image file to use to recover to your NVMe drive.
- Uninstall the MS hotfixes, leave the Samsung driver installed, then, create a new backup image file to use to recover to your NVMe drive.
- Leave the MS hotfixes installed and the Samsung drivers installed. create a new backup image file to use to recover to your NVMe drive.
In choice 1 your result should be a working NVMe boot drive with a MS driver.
In choice 2 your result should be a working NVMe boot drive with a Samsung driver.
In choice 3 your result is a question. If the hotfixes and the Samsung version 3.0 driver do not conflict then all should be fine. If the hotfixes and the Samsung driver conflict then it is possible that the drive will not boot. It is possible that it will boot but will BSOD at some point of randomly.
So the choice is your to make. All of the above is why it was recommended that you make a backup image file to work with instead of cloning the drive. If you choose choice 3 for example and it does not work you can start over with one of the other choices. If none of them work then you still have your working Win 7 SSD to fall back on because you will be working with a image file of that drive instead of the drive itself.
I hope this answers most of your questions. Thanks for being patient with us here as well.
Well i just tried with CSM disabled and it wouldn't even boot into the bios, well no video signal and the orange led on the mobo static (lit) gave a Q code of A9 froze at that point, so i cleared the CMOS, and lost my settings So won't be trying that again, why are what should be straightforward things like this made so bloody difficult ??
What i do not understand is why the MPV USB rescue image won't load, as the bios don't have a clue as to which hotfixes or drivers are installed on that backup image, and the MPV tool doesn't load anything from it at boot, so why is it hanging still? I could spend many more hours uninstalling hotfixes or drivers, How can this be causing the program to stop at the start screen and not even load Acronis, it makes no sense to me
3,Leave the MS hotfixes installed and the Samsung drivers installed. create a new backup image file to use to recover to your NVMe drive.
Is what i have just tried same screen it still isn't even loading Acronis so, It wasn't just the screen resolution, as you can see from the log i posted before,
so until that is resolved i can't progress further so matter what i change in the bios, or what i uninstall because i can't even get to recovery of my backup to test what works or doesn't work,
this is where i'm at and the hurdle i need to overcome, as said i'm sick of disconnecting drives and reconnecting them, if i had another PC it wouldn't as bad
So how can i get to the stage of being able to find out which of those 3 options will work , because right now I'm not even close to doing that i have built the USB image( MVP) As suggested and no change I don't know what to try Acronis directly using PE via it? that's all i can think of
Any suggestions what i can try other than give up?
dave wrote:Well i just tried with CSM disabled and it wouldn't even boot into the bios, well no video signal and the orange led on the mobo static (lit) gave a Q code of A9 froze at that point, so i cleared the CMOS, and lost my settings So won't be trying that again, why are what should be straightforward things like this made so bloody difficult ??
What i do not understand is why the MPV USB rescue image won't load, as the bios don't have a clue as to which hotfixes or drivers are installed on that backup image, and the MPV tool doesn't load anything from it at boot, so why is it hanging still? I could spend many more hours uninstalling hotfixes or drivers, How can this be causing the program to stop at the start screen and not even load Acronis, it makes no sense to me
-------------
Dave PM Mustang. I'm not sure if you're building with ADK or WinRE, but there may be an issue with Windows 7 builds of the MVP tool using WinRE. If you're using the ADK build, and only using the default "custom drivers" that came with it, it shouldn't be freezing.
Bobbo_3C0X1 wrote:Dave,
I would remove the Samsung Drivers since you have the Microsoft drivers and hotfix applied. I've also ready that there are conflicts in Windows 7 (I have both in Windows 10 without issue though). This could still be why you're seeing a bad driver error after restore.
CSM is only needed when you want the option to legacy (MBR boot). It shouldn't hurt to have it enabled or disabled though, as long as you're still are picking to boot the recovery drive in UEFI mode.
Also, I can't tell if you are injecting the custom drivers and/or the system drivers since the log is cut off. Just want to make sure you are selecting to use the custom driver option with just the default drivers in the folder.
And to be sure, you're using the 18.2 builder or something earlier?
Well i can only tell you what happened when i disabled it lost video signal to my monitor Q Code A9 , and having the usbflash drive in made no differece my only option was to clear the cmos , so that can stay enabled ,whilst i get what you are saying about conflicts, they won't be causing the issue that is preventing me from actually getting to the point of attempting to restore the image, I originally did think that it was MS hot fixes or samsung driver not both, but i was rightly or wrongly persuaded other wise ,
Bobbo_3C0X1 wrote:dave wrote:Well i just tried with CSM disabled and it wouldn't even boot into the bios, well no video signal and the orange led on the mobo static (lit) gave a Q code of A9 froze at that point, so i cleared the CMOS, and lost my settings So won't be trying that again, why are what should be straightforward things like this made so bloody difficult ??
What i do not understand is why the MPV USB rescue image won't load, as the bios don't have a clue as to which hotfixes or drivers are installed on that backup image, and the MPV tool doesn't load anything from it at boot, so why is it hanging still? I could spend many more hours uninstalling hotfixes or drivers, How can this be causing the program to stop at the start screen and not even load Acronis, it makes no sense to me
-------------
Dave PM Mustang. I'm not sure if you're building with ADK or WinRE, but there may be an issue with Windows 7 builds of the MVP tool using WinRE. If you're using the ADK build, and only using the default "custom drivers" that came with it, it shouldn't be freezing.
win 10 ADK and win PE addon
Dave,
Sorry for slow response time, family needs took precedence.
In your bios in Advanced Setup. Click the Advanced tab then, PCH Storage Configuration
- Verify SATA controller is set to - Enabled
- Set SATA Mode to - RAID
Go back one screen then, select Onboard Device Configuration.
- Set SATA Mode Configuration to - SATA Express
Go back one screen. Click on the Boot tab then, scroll down the page to CSM. Click on it to go to next screen.
- Set Launch CSM to - Disabled
- Set Boot Device Control to - UEFI only
- Boot from Network devices can be anything.
- Set Boot from Storage Devices to - UEFI only
- Set Boot from PCI-E PCI Expansion Devices to - UEFI only
Go back one screen. Click on Secure Boot to go to next screen.
- Set Secure Boot state to - Disabled
- Set OS Type to - Windows UEFI mode
Go back one screen. Look for Boot Option Priorities - Boot Option 1. Click on the down arrow in the outlined box to the right and look for your flash drive. It should be preceded by UEFI, (example UEFI Sandisk Cruzer). Select it so that it appears in this box.
This should complete your bios setup for UEFI boot. If you do not see your flash drive listed then there is a problem.
Maximus hero vii mother board manual
Is it the bios that is definatelystopping the usb tool from booting into acronis?