Towards the end of the install you are asked to enter login details. Microsoft suggest a Microsoft account with an email login. You might not want to do this (can be changed later if you desire) and you can select Offline Account on the same windows and use "Kent" and a password as you are doing at present. Your choice. Edit... There aren't many options to select during the install but if you feel you have made a mistake, no problem. Delete all partitions on the SSD and start again.
Hello @Brian K, Thanks again! Any and all advice is very much appreciated! I am sure my install of both a SSD and Windows will go smoothly with all the help that you have given me...
You should do this after Win10 has been installed... http://www.terabyteunlimited.com/ucf/viewtopic.php?f=2&t=427 I was playing with Fast Startup and corrupted the partition on a USB external HD.
I have a similar situation and hope the OP doesn't mind if i jump in here. I just purchased a used but in excellent shape "Dell Precision m4600" that came with a regular hard drive which i plan shortly to replace with a SSD. The video card is an ATI Firepro and several users have apparently messed up the bios installing windows 10 using UEFI instead of Legacy which my m4600 is set at. Would it be wise then to just stick with legacy when setting up the new SSD? If i choose to use Bitlocker in windows 10 pro under legacy bios, would it still function?? Thanks. http://en.community.dell.com/support-forums/laptop/f/3518/t/19478316?pi41097=1
tobacco, That's what I'd do too. Install Win10 in MBR/Legacy mode on a blank SSD. I've only used BitLocker on GPT disks but I think it works on MBR disks.
Kent, Of interest. The Microsoft Reserved Partition (MSR) is not seen in Disk Management but it is seen in Macrium Reflect and Diskpart.
Hello @Brian K, Thanks for that info. I thought I remembered something about one of the partitions not showing in Disk Management. Your post will alleviate confusion for me later as I am sure I would have came across this during my install and set-up process. Thanks also for the reminder about disabling fast startup. I have always done it since that was posted at TeraByte.
Thanks for the little push to stick with Legacy as everything went smoothly using a bootable usb thumb drive via microsoft's media creation tool. Couldn't believe how fast the process completed (Windows 10 Pro) on a SSD. Only 1 issue remains (seems to be common) that i spent a few hours online trying to figure out is - i have lost the ability to change the screen brightness. I can only do it in BIOS. ATI Firepro and Generic PNP Monitor drivers have been updated but still no change
Maybe this well help you, if you haven't already seen this: https://www.youtube.com/watch?v=lqnLAMfMPr8
Roger - You "DA MAN"!!! I watched several Youtube videos yesterday but did not see that one which corrected this issue. Thanks so much
Hello @Brian K, I apologize for the delay in responding back about my status as I had posted previously that I would receive the new system on Oct 13 (which I did) and then proceed with the fresh install of 1709 on a new SSD on Oct 17. I had a bit of a health scare here which put me out of circulation for 8 days but now I am back. Heck, I did not even get the new system unpacked until yesterday. I went through all the steps that we had discussed and got to the actual OS install. I was going to time it but.... I started the install, went to to get a cold glass of water, and came back. The install had already finished! I could not time it as I was away when it finished. I think it was around five minutes to complete but I know it took no longer than 10 minutes. In any case, unbelievably fast compared to well over an hour on my old system. All has been working as expected as I steadily churn along installing my software preferences and modifying the system to my liking. Thanks for all of your help as it made this process go glitch free for me, which I greatly appreciate! Just a FYI - A screenshot of Disk Management:
Kent, I'm glad you are in good health again. Your screenshot is excellent. As previously discussed, the MSR doesn't appear. You seem on top of Win10 but let us know if we can be of help. Have you disabled Fast Startup?
Hello @Brian K, The health is just one of those things being old and disabled You get used to it but it is always nice to be in as good health as possible. I just finished setting up Macrium Reflect and all four partitions do appear there as expected And yes, I did remember to disable Fast Startup...
Hello @Brian K, Well, I got everything to my liking so just prior to making my first image, I decided to test out everything within Macrium and then make an image. Create Rescue Media USB - no issues. Create Recovery Boot Menu Option - no issues. Test Rescue Media USB - no issues. Test Recovery Boot Menu Option - BSOD. Oh well, I opened a support ticket with Macrium. Note: Edit to remove spoiler "Support Ticket" from this post as I did not have permission from Macrium to post it.
Hello @Brian K, I do have IFL/IFW as well. I had planned to use Macrium first for a while until my health was 100% as it is easiest without much learning concerning UEFI systems. Later when I would have more time and my health a bit better, I had planned to install TeraByte and learn it. One reason is I have never liked simple mode and now for the time being did not feel like delving into IFL/IFW and a new learning curve. I have opened a support ticket with Macrium and if I do not hear back in 72 hours, Macrium may be history on my machine. I may make the switch to TeraByte 100%. I just thought I would give Macrium time to respond with at least a cause for the BSOD. I must admit though my confidence was a bit taken back when I could not upload a compressed dump file to their support system as the file size was too large (45 MB to 50 MB was too large). One would think that on a support system dealing with software that installs drivers, the max limits on file size would at least be able to handle a dump file. Keep in mind the original dump file was over 500 MB and with 7z I was able to reduce it down to about 48 MB. Very surprising that I could not upload it. Yes, BIOS set to AHCI for sure. All BIOS settings that we discussed were double verified and correct (in fact Dell default out of the box BIOS settings were exactly what I wanted). If Macrium does not respond within 72 hours, I may need your help setting up IFL/IFW and/or at least point me to some good knowledge base articles. Keep in mind I will want to be using normal mode, not simple mode. Macrium has had growing issues with version 7 but I will let support decide for me whether I will move on. Their support, also at least, used to be excellent. 72 hours is very reasonable as to at least try and find a cause (if not fix/patch) for my issue. I have gave them plenty of information to work with and have the dump files available, so they have no excuse not to respond.
Hello @Brian K, After a troubleshooting session first thing this morning with Macrium Support, the issue was resolved. It was a conflict with HitmanPro.Alert and after uninstalling HMP.A, the issue was resolved. In my case it was specifically HitmanPro.Alert 3.7.0 build 720 BETA as that was the version that I was running. I do not know if the issue will occur with the latest stable version of HMP.A or not. I have asked asked Macrium Support for permission to use the contents of the support ticket to post here to expedite the process of reporting the issue to Sophos. I have removed the spoiler of the support ticket from post # 41 awaiting approval to use. I should have known better throwing a beta software into the mix before I got my new system setup and my first image taken. It is always fun relearning old lessons...
Hello, Macrium Support gave me permission to use the contents of the support ticket to expedite and facilitate the posting of the issue: Spoiler: Original Support Ticket Hello, I retired my old system and moved my license to a new Dell XPS Tower 8920 system: Windows 10 Pro 64-bit Version 1709 (OS Build 16299.19) (UEFI) Macrium Reflect Home 7.1.2646 64-bit (UEFI) When booting to the Recovery Environment using the Recovery Boot Menu Option, I get a BSOD and then my system reboots again. The error on the BSOD is: Page Fault in Non Paged Area Once I am back in Windows, Reliability History shows three events have occurred: Source Intel® PROSet/Wireless Zero Configure Service Summary Stopped working Date ?10/?23/?17 19:29 Status Report sent Description Faulting Application Path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe Problem signature Problem Event Name: BEX64 Application Name: ZeroConfigService.exe Application Version: 19.60.0.0 Application Timestamp: 58d16fa6 Fault Module Name: ZeroConfigService.exe Fault Module Version: 19.60.0.0 Fault Module Timestamp: 58d16fa6 Exception Offset: 000000000022af80 Exception Code: c0000409 Exception Data: 0000000000000007 OS Version: 10.0.16299.2.0.0.256.48 Locale ID: 1033 Additional Information 1: d918 Additional Information 2: d9186ba6dae49e9fb237bd671bcccbfa Additional Information 3: 0608 Additional Information 4: 060872bd12942eae20a4fcf350674aa2 Extra information about the problem Bucket ID: 62133ed8c4bb23b48c5b679e029f70d6 (116353518053) Description The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffffffffffffd0, 0x0000000000000002, 0xfffff8014755c463, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f6183fa0-3d4b-473b-9ced-5d01e4bbf17b. Source Windows Summary Shut down unexpectedly Date ?10/?23/?17 19:32 Status Not reported Problem signature Problem Event Name: BlueScreen Code: 50 Parameter 1: ffffffffffffffd0 Parameter 2: 2 Parameter 3: fffff8014755c463 Parameter 4: 0 OS version: 10_0_16299 Service Pack: 0_0 Product: 256_1 OS Version: 10.0.16299.2.0.0.256.48 Locale ID: 1033 Files that help describe the problem 102317-16718-01.dmp sysdata.xml MEMORY.DMP WERInternalMetadata.xml memory.csv sysinfo.txt I am no export and do not know how to proceed but the BSOD seems to occur as the Recovery Enviroment is loading with the Intel® PROSet/Wireless Zero Configure Service. Note that I can boot to the Recovery Environment using a USB. The only memory dump that I could get access to I have zipped and tried to attach but at 50 MB it is to large and not allowed. I am also attaching information about my system from msinfo32. If you need anything else, please do not hesitate to ask.... Best regards, Kent Spoiler: Reply # 1 Hi, Thanks for contacting us It is likely that wireless driver which is not supported in PE is causing the blue screen on your system when you try and boot into Recovery Environment using the Boot Menu. Please open the folder C:\boot\macrium\Drivers\Network and delete any folders from within that path. Once you have done this please try booting into the Recovery Environment using the Boot Menu again. Please let me know if the results differ. Kind regards, Macrium Support Spoiler: Reply # 2 Hello, I tried what you asked. There is both good news and bad news... First the bad news: I went to the location C:\boot\macrium\Drivers\Network and deleted any folders from within that path. I then tried booting into the Recovery Environment using the Boot Menu again. However, there was a slightly different entry in Reliability History. Now the good news: The different entry in Reliability History was: Source Windows Summary Shut down unexpectedly Date 10/24/17 10:17 Status Report sent Problem signature Problem Event Name: BlueScreen Code: 50 Parameter 1: ffffffffffffffd0 Parameter 2: 2 Parameter 3: fffff802df2cf463 Parameter 4: 0 OS version: 10_0_16299 Service Pack: 0_0 Product: 256_1 OS Version: 10.0.16299.2.0.0.256.48 Locale ID: 1033 Extra information about the problem Bucket ID: AV_INVALID_hmpalert!unknown_function One of my security products that I have used for a long time is HitmanPro.Alert, website: https://www.hitmanpro.com/en-us/alert.aspx - download: http://test.hitmanpro.com/hmpalert3b720.exe I decided to do a test by the following: Restored the folder that you previously asked me to delete. Uninstalled HitmanPro.Alert Rebooted. Boot into the Recovery Environment using the Boot Menu. This time the Recovery Environment was booted into successfully without any BSOD. This seems to support the theory that HitmanPro.Alert somehow interferes with Macrium's Recovery Environment using the Boot Menu. Note that I am a beta tester for Sophos so the download link I gave points to the latest beta version. I do not know if this issue will occur with the latest stable version or not. I assume since this issue comes from a conflict with a third party security product, there will be probably nothing you can do on your end. The only immediate fix for now is to not install HitmanPro.Alert. Thanks for your help as it led me to identify the actual issue. I will report this issue of course to Sophos and I ask you for permission to to use the content of this support ticket in the reporting process. That would be greatly appreciated and make my reporting of the issue much easier. Best regards, Kent Spoiler: Reply # 3 Hi, Thanks for getting back to us. Glad to hear you managed to solve your issue. Feel free to reference the support case if you need to. If you have any other technical Reflect related queries feel free to contact us again. Kind regards, Macrium Support
Hello, FYI: I have posted about this issue between Macrium and HMP.A BETA in the appropriate threads: Macrium Reflect and HitmanPro.Alert BETA.
Hello @Brian K, Yes, it was. Macrium Support responded promptly (within 12 hours) and guided me with the troubleshooting steps to isolate the issue quickly.