PDA

View Full Version : Windows 10 Recovery - Reference - The need to replace Microsoft Windows Recovery



NeoBeum
09-30-2017, 11:47 AM
Sorry for spammy posts - but I wanted to keep each section seperate - as they are very large walls of text - but very important for each section - so, this is the only way to seperate it. I will eventually collate the whole project after I finish.

So, let us begin.


Why is the default Windows Recovery that is created automatically during Windows Setup bad?

1) If you buy a retail version of Windows to upgrade, or clean install - you will lose your OEM Recovery, unless you make a partition image of the original drive, and apply it to your new installation.

2) Replacing Hard Drives will also require an image of the original drive.

3) The partition layout Microsoft recommends and the partition layout Windows actually choses to use - are not the same.

4) Unless you implement a Push Button Recovery - Windows Recovery - actually does more harm than good.

Typically, You will only ever need to use your recovery options - if there is something terribly wrong, or to clean the device for resale.
Unfortuately - if you were attempting to recover from device failure due to incorrect drivers - Windows Recovery - will retain every driver that has been installed on your system.
After the initial recovery process boots after wiping the program files from the computer - the driver installation phase begins.
Windows will choose the latest date drivers that match hardware ID. Unfortunately for you, if this device reported to the System that it was operational - but it's behaviour actually caused instability - that was your most recent driver - and Windows will select that first.

5) The push button reset that ASUS provides, is somewhat better - but still - not immune to the drivers being loaded in to the driver store.
Push Button Reset - is a comlete image of how the Operating System, after Customisation, that is applied to the drive that the user originally had the Windows installation. This is why the OEM partition is significantly larger than installation media. It must be large enough to have a fully expanded Windows installation, and extra room for scratch.

During major version updates - dynamic updating of these images in the hidden recovery partitions are also updated - depending on the flags chosen by OEM or during setup.

NeoBeum
09-30-2017, 11:51 AM
Let us explore:

As some of you may know - I've been working on a CustOEM Recovery Disk for ASUS Notebooks - here is an example of the drivers I load in to the Preinstallation environment before Windows Setup.


PS C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools> DISM /Image:E:\WinROG\PE\mount /Get-Drivers /Format:Table

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

Obtaining list of 3rd party drivers from the driver store...

Driver packages listing:


-------------- | ------------------- | ----- | ----------- | ---------------------------- | ---------- | --------------
Published Name | Original File Name | Inbox | Class Name | Provider Name | Date | Version
-------------- | ------------------- | ----- | ----------- | ---------------------------- | ---------- | --------------
oem0.inf | nvme.inf | No | SCSIAdapter | Samsung Electronics Co., Ltd | 13/10/2015 | 1.4.7.16
oem1.inf | lynxpointsystem.inf | No | System | INTEL | 18/07/1968 | 10.1.2.86
oem2.inf | null_hecisystem.inf | No | System | INTEL | 4/01/2013 | 0.0.0.1
oem3.inf | heci.inf | No | System | Intel | 20/06/2017 | 11.7.0.1032
oem4.inf | intelpcc.inf | No | System | Intel | 4/09/2014 | 1.0.0.1018
oem5.inf | iastorac.inf | No | SCSIAdapter | Intel Corporation | 10/04/2017 | 14.8.16.1063
oem6.inf | iaahcic.inf | No | HDC | Intel Corporation | 10/04/2017 | 14.8.16.1063
oem7.inf | atk0100.inf | No | System | ASUS | 13/05/2009 | 1043.2.15.75
oem8.inf | atk4001.inf | No | System | ASUS | 11/05/2015 | 1.0.0.4
oem9.inf | asustp.inf | No | Mouse | ASUS | 10/04/2017 | 1.0.0.296
oem10.inf | asusdigifilter.inf | No | HIDClass | ASUS | 13/01/2017 | 12.0.0.3
oem11.inf | genestor.inf | No | USB | Genesys Logic | 20/04/2017 | 4.5.1.7
oem12.inf | tbt81x.inf | No | System | Intel(R) Corporation | 11/07/2016 | 16.2.51.2
oem13.inf | netwbw02.inf | No | net | Intel | 5/04/2017 | 18.33.7.2
oem14.inf | ibtusb.inf | No | Bluetooth | Intel Corporation | 13/02/2017 | 19.40.1.1
oem15.inf | rt640x64.inf | No | Net | Realtek | 27/06/2017 | 10.19.627.2017


Now, here is the driver list for my hidden recovery partition.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:E:\WinROG\RE\mount /Get-Drivers /Format:Table

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

Obtaining list of 3rd party drivers from the driver store...

Driver packages listing:


-------------- | ---------------------- | ----- | ----------- | ------------------------------ | ---------- | ---------------
Published Name | Original File Name | Inbox | Class Name | Provider Name | Date | Version
-------------- | ---------------------- | ----- | ----------- | ------------------------------ | ---------- | ---------------
oem0.inf | nvme.inf | No | SCSIAdapter | Samsung Electronics Co., Ltd | 13/10/2015 | 1.4.7.16
oem1.inf | iaahcic.inf | No | HDC | Intel Corporation | 17/11/2015 | 14.8.1.1043
oem2.inf | intelpcc.inf | No | System | Intel | 4/09/2014 | 1.0.0.1018
oem4.inf | ssm_ser2.inf | No | Ports | SAMSUNG Electronics Co.,Ltd. | 25/11/2009 | 5.12.0.0
oem5.inf | atk4001.inf | No | System | ASUS | 11/05/2015 | 1.0.0.4
oem6.inf | uvhid.inf | No | HIDClass | Unified Intents AB | 6/07/2016 | 11.56.12.0
oem7.inf | hspusb.inf | No | USB | MobileTop | 18/08/2009 | 2.1.2.0
oem8.inf | lgsfusbfilt.inf | No | HIDClass | Logitech | 19/04/2013 | 8.46.17.1
oem9.inf | lgvirhid.inf | No | HIDClass | Logitech | 13/06/2016 | 8.85.75.0
oem10.inf | ssudrmnet.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem11.inf | ssudbus.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 24/08/2016 | 2.12.4.0
oem12.inf | ssm_bus.inf | No | USB | SAMSUNG Electronics Co.,Ltd. | 25/11/2009 | 5.12.0.0
oem13.inf | ssudmarv.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem14.inf | ss_bbus.inf | No | USB | Samsung Electronics Co., LTD | 19/09/2009 | 5.0.0.0
oem15.inf | vmci.inf | No | System | VMware, Inc. | 25/05/2016 | 9.8.6.0
oem16.inf | ekbdflt.inf | No | Keyboard | Eset spol s r. o. | 24/05/2016 | 9.0.382.0
oem17.inf | sscdbus.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 30/11/2012 | 5.30.14.0
oem18.inf | asustp.inf | No | Mouse | ASUS | 24/02/2016 | 1.0.0.262
oem19.inf | iastorac.inf | No | SCSIAdapter | Intel Corporation | 17/11/2015 | 14.8.1.1043
oem20.inf | wacomrouterfilter.inf | No | Mouse | Wacom Technology | 9/03/2016 | 3.5.0.5
oem21.inf | ibtuart.inf | No | System | Intel Corporation | 9/01/2017 | 19.40.1702.1059
oem22.inf | ss_conn_usb_driver.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem23.inf | ssudobex.inf | No | Ports | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem24.inf | ftdibus.inf | No | USB | FTDI | 26/08/2014 | 2.12.0.0
oem25.inf | vboxusb.inf | No | USB | Oracle Corporation | 28/04/2017 | 5.1.22.0
oem26.inf | uvhid.inf | No | HIDClass | Unified Intents AB | 30/01/2017 | 16.35.34.0
oem27.inf | ggsomc.inf | No | USB | Sony Mobile Communications | 10/11/2014 | 3.1.0.0
oem28.inf | nvswcfilter.inf | No | Mouse | NVIDIA | 19/07/2016 | 8.16.22415.53
oem29.inf | wachidrouter_pro.inf | No | HIDClass | Wacom | 9/03/2016 | 3.5.0.5
oem3.inf | genestor.inf | No | USB | Genesys Logic | 13/07/2015 | 4.5.0.6
oem30.inf | heci.inf | No | System | Intel | 28/03/2016 | 11.0.5.1189
oem31.inf | sscesdm2.inf | No | Ports | SAMSUNG Electronics Co., Ltd. | 30/11/2012 | 5.30.14.0
oem32.inf | ssudsdb.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem33.inf | ss_bsdm2.inf | No | Ports | Samsung Electronics Co., LTD | 19/09/2009 | 5.0.0.0
oem34.inf | ftdiport.inf | No | Ports | FTDI | 26/08/2014 | 2.12.0.0
oem35.inf | lgjoyhid.inf | No | HIDClass | Logitech | 13/06/2016 | 8.85.75.0
oem36.inf | ssuddmgr.inf | No | Ports | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem37.inf | ss_bus.inf | No | USB | SAMSUNG Electronics Co.,Ltd. | 21/09/2009 | 5.0.0.0
oem38.inf | ssudserd.inf | No | Ports | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem39.inf | ssadsdm2.inf | No | Ports | SAMSUNG Electronics Co., Ltd. | 30/11/2012 | 5.30.14.0
oem40.inf | ekbdflt.inf | No | Keyboard | Eset spol s r. o. | 1/12/2016 | 10.0.379.0
oem41.inf | lynxpointsystem.inf | No | System | INTEL | 14/07/2015 | 10.1.1.9
oem42.inf | slabvcp.inf | No | Ports | Silicon Laboratories | 19/03/2014 | 6.7.0.0
oem43.inf | ssdudfu.inf | No | USB | SAMSUNG Electronics Co.,Ltd. | 1/06/2011 | 5.28.6.0
oem44.inf | vmusb.inf | No | USB | VMware, Inc. | 12/07/2016 | 4.2.0.0
oem45.inf | tbt81x.inf | No | System | Intel(R) Corporation | 9/06/2015 | 15.2.32.6
oem46.inf | wacdriverdl.inf | No | HIDClass | Wacom Technology | 12/08/2015 | 1.0.0.5
oem47.inf | nvswcfilter.inf | No | Mouse | NVIDIA | 25/08/2014 | 8.16.21500.1063
oem48.inf | lgbusenum.inf | No | System | Logitech | 13/06/2016 | 8.85.75.0
oem49.inf | sscebus.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 30/11/2012 | 5.30.14.0
oem50.inf | lgsfmouhid.inf | No | Mouse | Logitech | 24/09/2014 | 8.57.0.0
oem51.inf | ssadbus.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 30/11/2012 | 5.30.14.0
oem52.inf | ssudbus.inf | No | USB | SAMSUNG Electronics Co., Ltd. | 4/07/2016 | 2.12.3.0
oem53.inf | sscdsdm2.inf | No | Ports | SAMSUNG Electronics Co., Ltd. | 30/11/2012 | 5.30.14.0

The operation completed successfully.




Let us remove some of the drivers that have been causing grief - like the MTP USB outdated drivers, and the other drivers that I do not want installed.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:E:\WinROG\RE\mount /Get-Drivers /Format:Table

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

Obtaining list of 3rd party drivers from the driver store...

Driver packages listing:


-------------- | ---------------------- | ----- | ----------- | ------------------------------ | ---------- | ---------------
Published Name | Original File Name | Inbox | Class Name | Provider Name | Date | Version
-------------- | ---------------------- | ----- | ----------- | ------------------------------ | ---------- | ---------------
oem0.inf | nvme.inf | No | SCSIAdapter | Samsung Electronics Co., Ltd | 13/10/2015 | 1.4.7.16
oem1.inf | iaahcic.inf | No | HDC | Intel Corporation | 17/11/2015 | 14.8.1.1043
oem2.inf | intelpcc.inf | No | System | Intel | 4/09/2014 | 1.0.0.1018

oem5.inf | atk4001.inf | No | System | ASUS | 11/05/2015 | 1.0.0.4
oem6.inf | uvhid.inf | No | HIDClass | Unified Intents AB | 6/07/2016 | 11.56.12.0









oem16.inf | ekbdflt.inf | No | Keyboard | Eset spol s r. o. | 24/05/2016 | 9.0.382.0

oem18.inf | asustp.inf | No | Mouse | ASUS | 24/02/2016 | 1.0.0.262
oem19.inf | iastorac.inf | No | SCSIAdapter | Intel Corporation | 17/11/2015 | 14.8.1.1043
oem20.inf | wacomrouterfilter.inf | No | Mouse | Wacom Technology | 9/03/2016 | 3.5.0.5
oem21.inf | ibtuart.inf | No | System | Intel Corporation | 9/01/2017 | 19.40.1702.1059



oem25.inf | vboxusb.inf | No | USB | Oracle Corporation | 28/04/2017 | 5.1.22.0
oem26.inf | uvhid.inf | No | HIDClass | Unified Intents AB | 30/01/2017 | 16.35.34.0
oem27.inf | ggsomc.inf | No | USB | Sony Mobile Communications | 10/11/2014 | 3.1.0.0

oem29.inf | wachidrouter_pro.inf | No | HIDClass | Wacom | 9/03/2016 | 3.5.0.5
oem3.inf | genestor.inf | No | USB | Genesys Logic | 13/07/2015 | 4.5.0.6
oem30.inf | heci.inf | No | System | Intel | 28/03/2016 | 11.0.5.1189



oem35.inf | lgjoyhid.inf | No | HIDClass | Logitech | 13/06/2016 | 8.85.75.0




oem40.inf | ekbdflt.inf | No | Keyboard | Eset spol s r. o. | 1/12/2016 | 10.0.379.0
oem41.inf | lynxpointsystem.inf | No | System | INTEL | 14/07/2015 | 10.1.1.9


oem44.inf | vmusb.inf | No | USB | VMware, Inc. | 12/07/2016 | 4.2.0.0
oem45.inf | tbt81x.inf | No | System | Intel(R) Corporation | 9/06/2015 | 15.2.32.6
oem46.inf | wacdriverdl.inf | No | HIDClass | Wacom Technology | 12/08/2015 | 1.0.0.5

oem48.inf | lgbusenum.inf | No | System | Logitech | 13/06/2016 | 8.85.75.0

oem50.inf | lgsfmouhid.inf | No | Mouse | Logitech | 24/09/2014 | 8.57.0.0


The operation completed successfully.



Next, let us look at Microsoft's Recommended Partition Layout

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions

67805

Now, let's have a look at what is on Disk.
67808

67806 67807

The original partition Windows allocated grew too large - and was added after the Main partition, but the original partition was never changed - and is mostly empty.

NeoBeum
09-30-2017, 12:11 PM
The CustOEM Recovery Disk I am working on, will seperate a Push Button Recovery from updates - and maintain it's original image - throughout Windows Updates - the only time it will fail - is if the disk dies itself.

There will be an option to create a complete system image push button - or a compact version - the difference in size will be roughly 6-10 GB vs 20GB (Like OEM ASUS Recovery).

There will also be a Proper Hidden partition at the start of the disk - and will serve as a Flat Boot PE - if your system for some reason fails to boot and you're not at home - you can boot to this partition, and proceed with repair. This partition - will be less than 1GB - approx 600MB, but a 1GB partition is required. (perhaps not because Microsoft also recommends: wait for it)

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions


Recovery tools partition

This partition must be at least 300 MB.

This partition must have enough space for the Windows Recovery Environment tools image (winre.wim, typically between 250-300MB, depending on base language and customizations added), plus enough free space so that the partition can be captured by backup utilities:

If the partition is less than 500 MB, it must have at least 50 MB of free space.
If the partition is 500 MB or larger, it must have at least 320 MB of free space.
If the partition is larger than 1 GB, we recommend that it should have at least 1 GB free.
This partition must use the Type ID: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC.
The recovery tools should be in a separate partition than the Windows partition to support automatic failover and to support booting partitions encrypted with Windows BitLocker Drive Encryption.

We recommend that you place this partition immediately after the Windows partition. This allows Windows to modify and recreate the partition later if future updates require a larger recovery image.


Now I would like to make reference to an image above 67809

Need I continue?

I have tons and tons more of just .... I don't know... MSFT at it's finest.
Stay tuned.



PS: The CustOEM Recovery now has 3 Editions of Windows and Fits on to a DVD...(with the latest 2017-09 update & 2017 drivers) Stay tuned
67810



PS C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools> dism /Get-ImageInfo /ImageFile:V:\SOURCES\install.esd

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Details for image : V:\SOURCES\install.esd

Index : 1
Name : Windows 10 Education
Description : Windows 10 Education
Size : 14,689,350,899 bytes

Index : 2
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 14,870,668,738 bytes

Index : 3
Name : Windows 10 Home
Description : Windows 10 Home
Size : 14,684,985,530 bytes

The operation completed successfully.
PS C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools> dism /Get-ImageInfo /ImageFile:V:\SOURCES\re.esd

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Details for image : V:\SOURCES\re.esd

Index : 1
Name : Windows ROG™ DaRT Recovery Environment
Description : Windows ROG™ DaRT Recovery Environment
Size : 2,057,526,723 bytes

Clintlgm
09-30-2017, 05:47 PM
1. Correct, your far better off creating an OS Disk Image to recover in the long run.

2. Yes making it easy on your self using an image or straight up clone.

3. Partition lay out are depended on system spec's MBR or UEFI and will be set up by windows clean install. Again having an original Image saves worrying about this

4. I haven't used push button recovery! the original Recovery partition does have the Asus Drivers for your notebook contained. Basically if you use Window Reset it will put your notebook back to original how it was when you purchased it.
If you clean install you will lose the original recover partition it will be deleted and the original Windows native drives will be used.
If you run an WU Upgrade like CU AU these Version changing updated/upgrades will also overwrite your original drivers with windows native drivers and overwrite the recovery partition.

Also at this point we should mention all your original drivers and software are contained in the eSupport folder on the root of your C:\

So in the long run the original recovery partition is only good until the next Version changing WU. So the only real solution to having the ability to return your system to original configuration is to
1. have replaced the original hard drive by cloning or Image and removing the Orignal Hard Drive/SSD and storing it for the future
2. Have created a Disk/SSD Image before any configuration takes place and securing this Image in a secure Location other than your notebook.

5. It is my understanding that version changing WU, overwrite the recovery partition and Asus driver removed replaced by Windows Native drivers.
All in all it's a battle for our systems with MS WU. Windows thinks they have the best drivers for our hardware, which as we all know just isn't the case. With the Pro Version we can block driver updates from WU. With home version you'll have to check your drivers after every WU to insure you still have the best working ones for your notebook.

How to disable driver updates (https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html)

This is how I understand it it? The real solution for me is I have my original M.2 SSD in original condition stored in the box that my 960 Pro M.2 came in. I also have a secured Image of that SSD stored. I run daily back ups of my OS Drive and my Windows partition. I find it quite faster to restore a windows partition than to do a F9 restore or Windows reset. Pretty much the only reason to restore a full SSD would be to replace a failure or should something go wrong or corrupted on the boot sectors partitions.