I had to get a new computer ~ 6 months ago, and, of course, they (dell) wanted me to go with win10, but wearing my small-business hat, to purchase my workstation, they has the option to sell me win10 but with a free downgrade to win7 -- which I needed, as my intent was to transfer my
system image to the new computer.
That went off with a few bumps (like new computer's LSI (now avago) RAID drive would only allow you to configure the RAID if you booted in the UEFI secure mode -- but then the RAID would remaing as configured when you boot back into normal mode, but another bump I'm trying to iron out now (about 3-4 months after receiving the new computer, -- being able to boot into my windows repair environment .
I ran across a related block post on her, and mentioned that I couldn't begin to start at step 1, as it assumed you could boot into the WinRE image to do further steps. Trouble it is -- well I'm going to repost it here, so it can be answered in the forum rather than on the blog. I may get some hints on the blog, but it's not the best format for individuals responding back and forth, So...
(originally posted as a response to this blog entry):
I need to go back a step further -- to the point before you boot off the winRE image.
How do I disassemble, update and create a new winRE image that I can put on my hard disk so when Windows wants to boot into the rescue environment, it will bring up my new copy?
I have IO drivers that I need to have present on the winRE image in order for it be useful to perform the most basic Win Recovery tasks -- like keyboard, mouse and USB drivers, "seeing" the built-in/internal, SAS/SATA based hard disks, hard disks where the system image is located (without which, the standard winRE sees nothing except the built-in optical drives and the ramdisk on which winRE is running from).
Those are the most basic pre-requirements needed to begin to follow the information in this article.
Ideally, I'd like to add a video driver from my card vendor to allow accelerated 2D graphics like scrolling (among others), but that would be a convenience, admittedly.
So how can I create and complete those "assumed" (at least in this article) prerequisites so I can being to follow the instructions in the rest of this article (including being able to run chkdsk and sfc (which, currently, I cannot).
Thanks -- and would really appreciate this.
Lately, it seems I keep running into solutions that assume I'm already in some place that not accessible to my starting position (like recovering a MS-forum account of >15 years that uses my email address without using a text-messge (or how to get MS to accept my text-message number for authentication (it tells me that they refuse to send a message to my text-phone -- which has been used for the same type of purpose with other vendors and websites to do the same thing -- i.e. it works). The point being that in order to access their recovery solution, I first need to find out why they won't take my text-number, so they send me a text code, to do the original thing I was trying to do...(like, in this case, run in the windows RE).
(getting discouraged at constantly being told "you can't get there from here" (sigh).