Windows 10: Provisioning Package - Create in Windows 10
I get an error xcopy not recognized
Was that using the batch files, or typing in the commands yourself?
Figured it out. When I copied the code some reason it was including the dot before the code started.
A bit late to the party...but thanks for taking the time to post this up. A great tutorial
would you be able to use this process to transfer from an old win 10 pc to a new win 10 pc to transfer all your apps to the new one, then use scanstate and loadstate to update your settings?
Funnily enough I've been wondering the same thing.
I've not given it a try yet though - other things getting in the way at the moment so not had time to 'play' recently.
One issue is that any problems on the old PC will be brought forward to the new one and possibly give undesirable effects.
I've not used the scanstate->loadstate combination myself so not sure how well it works to copy user settings, but in theory that part should work.
Hello, last year (Summer 2015) I used these provisioning pack instructions to create custom recovery drives on three now three-year old Acer Haswell Laptops. I notice though that I still have the usmt.ppkg files on the c-drives. The files are as large as 20GB. Can I simply delete them at this point?
With Windows 10 Anniversary out now, and since I make system images of the machines regularly, I am thinking of simply keeping one bootable USB drive with Windows 10 on it, just in case I ever need to boot from a USB. Turns out, I am not fussed about reinstalling software (Office etc.) in case of calamity. Also, I used Brink’s Reset Recovery Image instructions to point the PCs to recovery copies of the install.wim on other partitions of secondary drives anyway. Note: the three machines are no longer identical, since I installed m-SATA SSDs in two of them this Summer, for example, using Kari’s instructions on moving the user folders back to the old hard disks. The provisioning pack files seem to have migrated via Macrium cloning to the new SSD c-drives, hence the desire to cut down on large files on the SSDs… Any supplemental advice appreciated. I can post this as well to the thread on bootable USB drives if advisable. Thanks!
Yes, you can just delete the usmt.ppkg.
Yes I agree.
The provisioning packages are mainly intended as a way of deploying software, and have the advantage that a less-technical user could run a Reset and have their software be reinstalled. But if you're happy to reinstall software yourself, I'd delete them as suggested.
I have now had a chance to try this.
I used a machine which had been running Windows 10 for a while, and which had various items of free software (no 'paid' licence) installed.
I ran scanstate to capture the software into a provisioning package.
Then I tried copying the provisioning package into the c:\recovery\customizations folder on a virtual machine with the same number of bits (32 bit in this case) and used the option to Reset.
Results were mixed!
Software like Firefox worked with no problem, but when it came to more challenging software, it was unhappy. Macrium Reflect Free just hung completely, and Microsoft SQL Server Express said it couldn't find a licence and needed to be re-installed. These software apps both have free and paid-for versions, so I'm guessing the info on the free licence got lost and confused the software when I started it.
The only caveat is that I had different users on the two machines - it's possible that I'd have had better results with identical users, but I wouldn't bank on it.
So I think it might work if you have a simple array of software, but anything complicated would cause an issue.
I was in the setup and I think i was on the licence agreement page. When I klicked accept, "what to keep" popped up on the top for an instant then was replaced with "making sure you're ready to install" which sat there saying "please wait" for about...
After some troubble with my PC I wanted to restart in safe mode, but it can't do that. Breaks off and write something about a "hard crash", only the taskbar works, and I can also ust winkey+R and start regedit aso.
Because of this I...
I'm surprised that on downloading the build there's no indication of its current progress or even WHERE it gets downloaded to.
I'd like a bit more control over this -- especially on the % download.
Read more at: Microsoft to highlight its 'One Windows' progress at Build 2014 | ZDNet