Factory MFT on a brand new HP Windows 10?

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 11
    Windows 7
    Thread Starter
       #11

    flybynite said:
    You want to avoid Windows 10 because all of its features aren't up and running before it is installed? I do not think you would find a shutdown button on ANY operating system, before it is up and running.
    I totally agree, but you miss the point of why I want to avoid Win10. It has nothing to do with a lack of power / shutdown before completing initialization. It has everything to do with a very long history I have with Micro$oft and how they choose to do business, some practices of which I have described in these posts.

    Here's one example: How long did it take me to go from first press of power switch on a brand new system to get to where I could interact with it? It took FAR longer than other operating systems, including Windows 7.

    I just find Windoze does not stack up to other operating systems, primarily unix variants. It is less efficient on resources, performs more poorly and is less reliable by design, primarily due to the registry. All op systems have their drawbacks, I just find those in Windoze harder to deal with, not to mention the philosophical issues I have with proprietary software --- woops, I just did
      My Computer


  2. Posts : 4,802
    Windows 10 ProWorkstation -- Whichever is highest build number.
       #12

    thomnet said:
    I totally agree, but you miss the point of why I want to avoid Win10. It has nothing to do with a lack of power / shutdown before completing initialization. It has everything to do with a very long history I have with Micro$oft and how they choose to do business, some practices of which I have described in these posts.
    Well you have your reasons I suppose. I happen to like the way they do business. I haven't had any problems what-so-ever with Microsoft.
      My Computer


  3. Posts : 3,453
       #13

    thomnet said:
    Duh, "making a copy" is precisely what I'm trying to do! Reading the info you linked, mostly the discussion is dealing with problems trying to use chkdsk on the active system drive. That isn't the case here.

    Also, I see using "copy" and restore as far more risky than using Micro$oft tools to repair the drive. However, I am not convinced this issue is a matter of a corrupt drive, now that chkdsk gives it a clean bill of health. Perhaps it's a bug in Macrium, perhaps some unusual condition / state of the drive Micro$oft intentionally mandates OEMs to employ to thwart drive cloning as a way to prevent OS piracy. Just speculation, but I wouldn't put it past them.
    If you can't access the data, obviously the drive is toast.
      My Computer


  4. Posts : 11
    Windows 7
    Thread Starter
       #14

    Superfly said:
    If you can't access the data, obviously the drive is toast.
    Obviously the drive is NOT toast, look at the chkdsk results.
      My Computer


  5. Posts : 3,453
       #15

    Can you access the data and copy it? even from Linux if need be. Why so hell-bend on a Macrium image - just copy the stuff, if need be, and reformat the thing, Geez!.
      My Computer


  6. Posts : 11
    Windows 7
    Thread Starter
       #16

    Superfly said:
    Can you access the data and copy it? even from Linux if need be. Why so hell-bend on a Macrium image - just copy the stuff, if need be, and reformat the thing, Geez!.
    B/C I have not found a nice, reliable and convenient backup program to use on Linux, surprisingly enough. Macrium is great, so is Acronis but I don't have a license for it.

    I could use dd in linux but shit that takes f o r e v e r !!!

    You can't just "copy" a Windows disk and expect it to work, with 763 posts here you oughta know that - Geez!

    Interestingly I just managed to use Macrium to make an image of the 16GB Recovery partition, which I believe should be able to restore the rest of the drive to factory fresh state. That is sufficient enough as a drive backup, assuming it's easy to launch it, like setting that partition bootable or using Hirens to boot it into recovery. Still have gaps in my UEFI knowledge, so not sure about that.
      My Computer


  7. Posts : 3,453
       #17

    LOL... Once you have the data, to create a restore is easy. Why image a FUBAR'd partition anyway?
      My Computer


  8. Posts : 1,579
    Windows 10 Pro
       #18

    thomnet said:
    B/C I have not found a nice, reliable and convenient backup program to use on Linux, surprisingly enough. Macrium is great, so is Acronis but I don't have a license for it.

    I could use dd in linux but shit that takes f o r e v e r !!!

    You can't just "copy" a Windows disk and expect it to work, with 763 posts here you oughta know that - Geez!

    Interestingly I just managed to use Macrium to make an image of the 16GB Recovery partition, which I believe should be able to restore the rest of the drive to factory fresh state. That is sufficient enough as a drive backup, assuming it's easy to launch it, like setting that partition bootable or using Hirens to boot it into recovery. Still have gaps in my UEFI knowledge, so not sure about that.
    As far as implementing factory restore have you simply tried that, starting at power down state and hammering F11 (I think it's that for your model, if not F4) on startup to access factory restore routine ?? - understood that option could have been borked by what happened so far but you could at least rule it out as an option.
      My Computer


  9. Posts : 11
    Windows 7
    Thread Starter
       #19

    Word Man said:
    As far as implementing factory restore have you simply tried that, starting at power down state and hammering F11 (I think it's that for your model, if not F4) on startup to access factory restore routine ?? - understood that option could have been borked by what happened so far but you could at least rule it out as an option.
    Alright, some real useful ideas here! Now we're talking! The drawback however is that I must reassemble the machine to try these ideas. I really want to have a way to restore the factory state of the HDD on a backup medium, so I can install anything on the drive and know I can get back to factory. That's one reason I chose to image the drive in another system.

    Does anyone here know for certain how to power off a brand new Win 10 machine, in a sysprepped state, ready for first power on (i.e. like the state systems are in as shipped from factory, before user pressed on button for first time)?

    I mean, if the whole reason for this hassle is due to the way I turned off the machine, how do you do it right BUT before you even begin to interact with setup?

    After opening box from retailer, turn it on, wait for the machine to reach a point where it's asking for the user's first inputs (i.e. after you stop waiting on the machine and the machine starts to wait for you), at this very point, how do you shut it down if using the power button is off limits?

    I think what I will do is reassemble the machine and see if it powers up normally as it did the first time. If so I'll see if I can find the key sequence to initiate a factory restore. I'll also see if I can figure out how to shut the machine off cleanly before completing setup.

    Now that I have a good backup of the system RECOVERY partition I should be able to wipe the disk entirely and restore that partition with macrium which in turn can restore the other partitions, IF I can find the right way to start the recovery process.

    I don't plan on another disassembly to pull the HDD, so hopefully the backup I have will provide the insurance to play. Crossing my fingers...
      My Computer


  10. Posts : 11
    Windows 7
    Thread Starter
       #20

    I reassembled the computer and it booted normally exactly like the first time. There is NO OPTION to power off the machine EXCEPT the power switch. Pressing the power switch once results in a hibernated state which is resumed when the power switch is pressed again. It was looking like I had no choice but to run through the setup.

    I decided to power off (hibernate), then remove the battery. When I put the battery back in and hit the power button it came back to the same state as it was for the first power on. I repeated this but the next time immediately after pressing the power button to turn the system back on I hammered F11, which started the recovery process.

    So now I am ready to install my alternate OS. I am using RMPrepUSB, which allows me to boot the USB HDD in either UEFI or MBR modes. With this system I cannot boot anything except UEFI media, but so be it, I'm moving on.

    I have no freakin idea why Macrium would not allow me to take a full disk image backup, but screw it, time to stop messing around.

    Man how I hate UEFI, so difficult to change basic options, requires at least 2 boot cycles, slow as a dog, no feedback to user for boot sequence, requires memorizing key sequences to change boot options, it just sucks.

    I can see why IT departments like it, but there oughta be options to turn on feedback for techie types, software developers and the like. I find UEFI very frustrating.
    Last edited by thomnet; 16 Apr 2016 at 19:22.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:47.
Find Us




Windows 10 Forums