New
#21
I have found several changes in the new reset feature and how windows 10 installs compared to prior versions..
Creating a Windows 10 Recovery Drive is a Window's Only recovery method..
On an MBR disk the recovery drive creates 3 partitions - System, OS and WinRE Tools (MBR Disk has 4 Partition Limit)
Also the WinRE partition is now the last partition, compared to being the first partition, in prior versions..
And resetconfig allocated all the disk space to the windows recovery..
Creating a recovery drive also creates a reconstruct.wim ( in prior versions a factory install.wim was required) you will now notice the rename from Install.wim to reconstruct.wim..
Here is another fun fact - I installed windows 10 on a MBR disk with 4 partitions - Vista - windows 7 - windows 8.1 and windows 10
Windows 10 placed the WinRE Recovery folder on the first partition (which is my vista OS and also the Boot Partition) along with a winre partition marker (tag)
So - if you decide to do a reset using the recovery drive created by windows 10 - expect everything on your hard drive to be wiped out.. Unless you edit the resetconfig and diskpart files..
And a little side note - since I find it faster to prep an install.wim and use recovery to apply the images to the partitions, rather then running through Setup
I would guess one could create a custom reconstruct.wim - instead..
I will post more of my findings after I look deeper into the reset.. The user profile is said to be carried over and I believe the system drivers - any installed programs are said not to be - this is just early testing for me..
The reconstruct.wim created was only 2.22GB when the original install.wim was 2.49GB
After mounting the reconstruct.wim - it does not follow the same layout or folder tree that an install.wim does..
You can add Windows desktop applications and other data to the device.
After doing this, you use the ScanState tool (user state migration tool) to capture the changes into a provisioning package so they can be used by the recovery tools.
Last edited by Kyhi; 08 Jul 2015 at 11:46.
just downloaded windows 10 RC ADK again
and when running scanstate to get the .ppkg of custonizations
get error message
So much for testing recovery and customizations - for now anyway, until the USMT is updatedSCANSTATE.EXE Version 10.0.10075.0
Only Windows XP, Windows Vista, Windows 7 and Windows 8 are supported as sources.
Unsupported OS Version: 10.0.10162
Failed
Compliance check failure; please check the logs for details
Yes I think Scanstate is the key. There's a SET command you can use to get further, but it still crashes in 10075. I'm also awaiting the next ADK..
just downloaded windows 10 RC ADK again
and when running scanstate to get the .ppkg of custonizations
get error message
SCANSTATE.EXE Version 10.0.10075.0
Only Windows XP, Windows Vista, Windows 7 and Windows 8 are supported as sources.
Unsupported OS Version: 10.0.10162
Failed
Compliance check failure; please check the logs for details
So much for testing recovery and customizations - for now anyway, until the USMT is updated
Hi
MSDN page suggests that
- Type the following command as a workaround to bypass an issue with version checking on Windows 10 Insider Preview.
set MIG_USMT_BYPASS_OS_VERSION=TRUE
Source : Deploy push-button reset features using ScanState (Windows Drivers)
My brother, who is not particularly tech-savvy, bought a new Vista-equipped Toshiba Satellite laptop several years ago, and one of the first things I showed him was how to do a system image.
Two machines later, and via Win 7, 8, and now 8.1 and I don't think he's ever taken a single one...
I take one at least monthly - more frequently if I make a lot of changes.
Wenda.
new error message2015-07-09 06:27:28, Info [0x000000] SCANSTATE.EXE Version 10.0.10075.0[gle=0x000000b7]
2015-07-09 06:27:28, Info [0x000000] USMT Started at 2015/07/09:06:27:28.073
2015-07-09 06:27:28, Info [0x000000] Command line: E:\USMT\scanstate.exe /apps /ppkg C:\Recovery\Customizations\ /o /c /v:13 /l:C:\ScanState.log
2015-07-09 06:27:28, Info [0x000000] Version check bypassed because MIG_USMT_BYPASS_OS_VERSION is set
2015-07-09 06:27:28, Info [0x000000] Version check bypassed because MIG_USMT_BYPASS_OS_VERSION is set
2015-07-09 06:27:28, Status [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING'
2015-07-09 06:27:28, Info [0x000000] Store root: C:\Recovery\Customizations\
2015-07-09 06:27:28, Info [0x000000] Store path: C:\Recovery\Customizations\
2015-07-09 06:27:28, Info [0x000000] Store file: C:\Recovery\Customizations\
2015-07-09 06:27:28, Info [0x000000] ICB Telemetry: This is an ICB extraction scenario, and SendTelemetry is enabled.
2015-07-09 06:27:28, Info [0x000000] Creating/Opening provisioning package C:\Recovery\Customizations\
2015-07-09 06:27:28, Info [0x000000] Creating provisioning package C:\Recovery\Customizations\
2015-07-09 06:27:28, Error [0x000000] Error creating the provisioning package. Error: 0x80070057
2015-07-09 06:27:28, Error [0x000000] Error while creating provisioning package store: Win32Exception: Error creating the provisioning package.: The parameter is incorrect. [0x80070057] long __thiscall Mig::CICBStore::Initialize(int,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *)
2015-07-09 06:27:28, Info [0x000000] Failed.
2015-07-09 06:27:28, Info [0x000000] A Windows Win32 API error occurred
Windows error 87 description: The parameter is incorrect.
2015-07-09 06:27:28, Info [0x000000] Windows Error 87 description: The parameter is incorrect.
2015-07-09 06:27:28, Info [0x000000] USMT Completed at 2015/07/09:06:27:28.245
2015-07-09 06:27:28, Info [0x000000] Entering MigShutdown method
2015-07-09 06:27:28, Info [0x000000] Leaving MigShutdown method
2015-07-09 06:27:28, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------
2015-07-09 06:27:28, Info [0x000000] * USMT error code 71:
2015-07-09 06:27:28, Info [0x000000] +-----------------------------------------------------------------------------------------
2015-07-09 06:27:28, Info [0x000000] | A Windows Win32 API error occurred
2015-07-09 06:27:28, Info [0x000000] | Windows error 87 description: The parameter is incorrect.
2015-07-09 06:27:28, Info [0x000000] +-----------------------------------------------------------------------------------------
I figured the RC in the ADK was Release Candidate
I don't think so, now