Windows 10: Win10 performance issues complex setup

My desktop does not meet requirements for Win11, so it is Win 10.I have historically used virtual machines originally created in VMWare to separate work, personal email etc., dev, etc. Each VM client is fully licensed. I'm trying to set up a new VM for software development, it has had very little use since I originally created the client VM which was when I bought the Win10 license. Client is Win10 x64 with 8GB Ram, 4 processor cores, and plenty of HD space around 50GB. The only software installed is Office19 and Mindmaps Pro MS product. I've run the windows file checker/repair, and

:)

 

Complex Setup Upgrade Guide


Hello,

TL;DR version at the bottom

I've been trying to update my Vaio Netbook from Windows 7 to 10, unfortunately with no luck up until now. I will explain in a few steps and hopefully someone else will find this useful as well:

First of all my setup. A bit complex, as I have a quad boot of the following partitions on my Setup

Primary #1 Windows 7 Recovery
Primary #2 Windows 7 (original OS that came with the laptop)
Primary #3 Windows 8 (installed after windows 7)
Extended #4 Several Logical Partitions with two Linux installations

So, currently I have the following bootloaders: GRUB (linux bootloader), Windows 7 Bootloader, Windows 8 Bootloader.

I decided a few days ago that I no longer wanted 7 & 8, and that I would nuke the Windows 8 and upgrade my Windows 7 to 10 all the way. I went ahead and simply formated the Windows 8 partition (played around and reallocated space / extended other partitions), refreshed my GRUB bootloader's entries and noticed that Windows 8 Bootloader was still there. I tried to boot into it, and it simply started loading a Windows 8 Recovery so I just rebooted the system - thinking that the Windows 8 bootloader was just left over and was useless.

I then downloaded the Windows 10 media creation tool, tried to update the system but it rebooted with an error. Can't recall what the error was, but I wasn't too mad since I knew my installation was a bit complex. I then went on trying to install Windows 10 about 7 more times, failing each time after the initial reboot with the following error:

Code:

Code:

The installation failed in the SAFE_OS phase with an error during BOOT operation

with an error code of:
Code:

Code:

0xc1900101 0x20017

Every single time, no matter whether I chose to keep nothing, everything, tried updating Windows 7 first (which ended up breaking my Windows Update, and then breaking my Network Drivers), tried removing several devices as suggested in a lot of posts with the same error code in Windows7/8/10 forums, all resulting in the same error.

I then remembered that I still have two Bootloaders for Windows, and I figured that the installer probably fails because each time the machine reboots I choose to launch the Windows 7 bootloader, which is probably used as a hack by the devs to tell that something went wrong. So, this time after running the windows upgrade and the machine automatically reboots, I choose the Windows 8 bootloader and all of a sudden the Windows 10 installation continues on my Windows 7 OS.

And here I am, after 2 days of reading relatively unrelated threads, thinking whether it was my fault or not. Surely, my setup was complex, but this simply means that if someone (for whatever reason) needs to have Windows 7 and Windows 8, and then chooses to upgrade Windows 7 to 10, things are gonna get messed up.

I understand that I am probably the only person to ever fall into this bug, but this also suggests that Windows Bootloaders might be a bit hard-coded, and don't keep in mind that other OS's might rely on the same setup - which shouldn't be the case when a Windows Upgrade is as strongly pushed as Windows 10 was. I am sure there are great reasons as to why Windows Bootloaders prefer to ignore everything the machine has to say about itself and do their own thing, but then we have bugs like this one.

I'm not really sure if developers read these forums, but if they do I'd like to hear a technical explanation of my bug.

TL;DR: Had Win7 & Win8 (installed after), tried to upgrade Win7 to Win10 and fell to the same ambiguous error over and over until I continued the installation through Win8 bootloader as a shot in the dark. Suggests possible bug in Windows bootloaders.

My only suggestion to other people who reach this thread by googling for the errors I posted is:

If you've ever installed multiple Windows instances on the same hard drive, the Bootloaders are probably kept and are causing you this issue.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Activation options for Win10 with instant clones

We have a secure (no internet access) lab environment setup to test and validate a VMWare VDI deployment of Win10 clients.

Our issue is activation of the Win10 clients as they require re-activation every time we logoff and back on because we are using instant clones.

Does anyone have any suggestions on the best way to resolve this? Here are the options we are considering and issues as we understand them:

• Setup a KMS server
  • Requires a Volume license, which is doable
  • Documentation says we must have a minimum of 25 hosts, we don' have that in our lab
• Use our MSDN account
  • No support for Win10 KMS license
  • No support for MKS activation
• Manually activate each time
  • Gonna spend a lot of time on the phone
  • Win10 has no grace period so machines are crippled w/o activation

Anyone have a thought or suggestions? I'm hoping I missed something.

Thanks