|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
This guide targets two separate but intertwined groups: Those who have recently upgraded from Win7 (or, less likely, Win8.1) and those who have upgraded from an earlier version of Win10 (likely the November Update, Version 1511) to a recent version (as of this writing, probably the Anniversary Update, Version 1607). [See the full post at: Windows 10 upgrade problems – and what to do about them]
Gunter Born has an interesting revelation about error 0xC0020012 on his Born City web site.
Concering the “Something Happened 0x80070005-0x90002” error:
0x80070005 stands for ERROR_ACCESS_DENIED
The extended error code 0x90002 should specify the phase, where the error occurs. Unfortunately 9 isn’t documented, 02 is probably SP_EXECUTION_OP_COPY_PAYLOAD. Details may be obtained from log files.
See:
http://borncity.com/win/2016/10/15/windows-10-analyze-upgrade-errors/
http://borncity.com/win/2016/07/05/how-to-decode-windows-errors/
https://technet.microsoft.com/en-us/itpro/windows/deploy/resolve-windows-10-upgrade-errors?f=255&MSPPError=-2147217396
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
What I would add, if your current configuration is valuable to you, is this:
Make BACKUPS! Before you make changes that could destroy your current system.
For example, make a System Image backup to an external USB drive. Such drives are not expensive. If something goes wrong, you can restore it and continue on from where you were before as though nothing had happened. It really works, and you don’t even need 3rd party software to do it.
I find it incredible that Microsoft places us in positions where our configurations and data can just be lost by their ham-handed in-place upgrade, now more than once a year. It’s not acceptable! Our time and work are valuable to us!
In the past adept computer professionals wouldn’t consider running an operating system that was installed as an in-place upgrade to an older operating system. We installed each new version of Windows afresh, and with good reason. Things worked right that way.
-Noel
As Win 10 is an acquired taste and you may want to try before you take the plunge give it a try in VHD first Virtual Box is good as is Hyper-V (if you have it Win7 doesent and I think Win8.1 Pro and up do) Or you can create your own right from the get go. This way you can check it as it will run on your system. Depending on your machine a capacity of about 100+ GB you should be fine unless you have a ton of stuff on there.
Bascially create an iso with the media creation tool specify for another machine and leave the settings button deselected. Create a USB or burn to disk using Rufus or your favourite disk burning tool.
Boot from your install media.
When you get to the Blue selection language etc screen hit SHIFT-F10
at the X:\ (prompt) type DISKPART
type LIST DISK
type SEL DISK 0 (if that’s the one for install)
type LIST VOL (to see/check where you want it)
type (doesent have to be in caps)
CREATE VDISK FILE=C:\WIN10.VHD MAXIMUM=40000 TYPE=FIXED
(every 1000=1GB type=fixed or type=expandable means the disk can grow with use but will not shrink not as stable in a production environment I prefer fixed)
type ATTACH VDISK
EXIT
EXIT
and your done set up as normal the newly created VHD will appear at the selection screen as unformatted space of the same size you specified, select that and off you go. That’s it really it will run and behave just as any normal installation. If you want to read/write to the new VHD like you would any other partition you need this utility. https://www.medo64.com/vhdattach/ otherwise you have to reattach the VHD every time you boot in to your “Real OS” (which can be a pain) naturally install this in to your real OS.
Not sure if Win10 home will support this either as “Guest” or “Host” system. Really only ever ran Pro and above at work and personal.
If you want to get rid of your new creation boot in to your real OS detach you VHD (if attached) type MSCONFIG in you run box delete the OS entry (carefully on multi-boot systems) it wont allow you delete your OS that your booted in to. Got to wherever you created your VHD and just delete it and your done.
Up to now it works on Win7 Ult & Ent, Win8.1 Pro & up Win10 Pro & up best thing is if it doesent work your not going to wreck anything.
(that’s strange ahh well I posted before and it disappeared ahh well here it is hope this works for you folks out there 🙂 )
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
