Upgrading Windows 8 To Windows 10

0 views

Skip to first unread message

Renita Lukins

unread,

Aug 3, 2024, 3:21:51 PM8/3/24

to vihiplighscar

I have a business grade HP machine still running Windows 7 that came with the machine.
I want to update it now to Windows 10.
The main link on the MS site for downloading the Update (22H2 - -us/software-download/windows10) is giving me an error on both my desktop and laptop machines when I go to launch the exe it downloads:

If I download the "Create installation media" file, will that give me the same option to "update over Windows 7" the exact same way the Update link would (if it was working properly, that is)?

If your windows are in good condition, taking steps to improve their efficiency may be the most cost-effective option to increase the comfort of your home and save money on energy costs. There are several things you can do to improve the efficiency of your existing windows:

First look for the ENERGY STAR label when buying new windows. Then review ratings on the energy performance label from the National Fenestration Rating Council (NFRC) to find the most efficient windows for your needs.

Note: The question is specifically asking how to upgrade npm, not Node.js. If you want to update Node.js over a CLI on windows, I recommend running winget upgrade -q NodeJS or use chocolatey for that.

If you get `wget : Could not find a part of the path .... "**, see below ...scroll down. Reading Web Response... It's at least punching through the firewall /proxy (if you have one or have already ran the code get through ...

The previous answers will work installing a new version of Node.js (probably the best option), but if you have a dependency on a specific Node.js version then the following will work: "npm install npm -g". Verify by running npm -v before and after the command.

The new installation added the new directory into my path variable after the old one. So the old installation was still the active one in the path. After removing C:\Program Files\nodejs\ from system path and C:\Users\...\AppData\Roaming\npm from user path and restarting the command line the new installation was active.

Maybe the least path was a local problem that has nothing to do with the new installation. I had two links to AppData\Roaming\npm in it. And maybe this can also be fixed by first uninstalling Node.js and installing the new version afterwards.

For the best way to update Node.js (at least for me), go to Then download the last version and install it in same folder you installed the previous version in - 1 min and it's done. You don't need to remove any old files.

Step 1: First, ensure that you already have Chocolatey installed. If not, use an administrative shell to install chocolatey through cmd.exe or PowerShell.exe. For more information, visit:

A common reason is an attempted "npm install npm" or "npm upgrade npm". As of today, the only solution is to completely uninstall and then reinstall Node.js. For a small tutorial, please see -npm-upgrade (dead link).

So this is what I did (worked for me):1. Download the latest installer from nodejs.org. Install node. It will update your node; everywhere (Powershell, cmd etc.).2. Install the npm-windows-upgrade package (npm install -g npm-windows-upgrade) and run npm-windows-upgrade.

I know that I can sign in with a personal Microsoft account (or create a local account), upgrade windows, join the device to AD and then switch to logging in with a corporate account. I would like to know:

In the OOBE, you can press SHIFT-F10 to open a console. I believe that Changepk.exe can be used to upgrade from Home to Pro given the right key. Will this work from the command line in the OOBE? It would save a lot of faff with unnecessary local accounts.

Once you hit the login screen, press F10 to open CMD. Technically you can open CMD while it's installing Updates but I don't recommend this because it will restart without warning and might interrupt the following process.

I wanted to add a note to the above answer. For many, they will have to press shift+f10 and maybe shift+fn+f10 to get the CMD to pop up. I don't have enough points to comment on amazing answer by Baa.

I want to thank you. I work for a small business. Well, not super small anymore, we have 80 employees now. But we were only 4 3 years ago. I buy computers mostly from Costco on sale and so they always have Windows Home. I have had to go through the steps of creating either a MS account user or local user in setup and then do the migration to Pro inside of windows. I had to install a bunch of software first too. Your trick really saved me a ton of time. I am so grateful!!! I am going to be using this trick for years to come. I setup 5-10 computers a month. We have pro keys but honestly it was more work entering them than your quick trick. I built an Azure active directory and use intune to keep all the computers organized. Your method instantly adds the new computer to my dashboard. This process took so much work before.

I checked Windows Update and it has not been updating since March. When I tell Windows to check for updates, it acts like it is checking, but it seems to say that for hours. If I attempt to restart the windows update service, it seems to never be able to shut down. My only remedy seems to be rebooting to get back to the point where I can tell Windows Update to check for new updates.

To disable IE enhanced security in windows server 2012 R2, launch the Server Manager, on the left hand side click on Local Server. On the right hand side click on the On link next to IE Enhanced Security Configuration. You will now see the Internet Explorer Enhanced Security Configuration box.

I've had been playing around with a 2012 VM and I had this issue. My solution (quick, insecure, etc etc) was to disable the IE Enhanced security on the server and it happily started talking to MS Windows Update. Not a solution for a real server, but it's a toy dev server and I'm ok with that.

I have recently have the same issues on my Server 2012 and all I did was disabled the Malwarebytes Service and updates downloaded right away. Try disabling any malware or anti-virus software you have because that could be the root caused.

We had this issue on some virtual servers migrated from a "cloud" provider back to our internal data center. The root cause was permissions to the %SystemRoot%\System32\catroot2 folder. There were a number of differences between the permissions on that folder on a healthy server vs those on the migrated server. I believe the key one was that TrustedInstaller didn't have full access.

When installing a OS fresh on a server I know that Intelligent Provisioning injects a lot of drivers, etc. during the install process. When doing an in-place upgrade that same injection process does not occurr so I thought it worth reaching out to HPE first in case there where possibly some drivers that might not get picked up during the upgrade. I'm assuming applying the latest SPP would have resolved that though.

I've still not been able to get my 2 servers that I in-place upgraded from 2012 R2 to 2016 to accept the cumulative windows updates. It's the same issue where the update process gets to 100% and then says it can't complete and rolls everything back. I was waiting for the 2023-09 update to see if the issue might have been related to the 2023-08 update but the behavior is the same. I have not opened a support request yet with Microsoft as it just might be easier to rebuild the servers than to deal with MS. One of the many things I read about windows updates not being able to complete is that the recovery partition is not big enough. Oddly enough, each of these servers has 2 recovery partitions, one is 450 MB, the other is 13.97GB. The 13.97 GB partition resides immediately after the 450MB paritition so if the update process is trying to enlarge the 450MB partition it will surely fail. According to the reagentc /info command, the WIN RE is pointing to the 450MB partition so it should be pretty save to delete the odd 2nd recovery partition and see if that makes a difference with the update process. It's worth noting that I've done an in-place upgrade on a 3rd server that does not have this odd 2nd recovery partition and it's accepting the cumulative updates just fine. I'm not sure how the 2nd recovery parition got created in the first place but deleteing it makes a lot of sense to me.

Thank you for getting back to me! Interestingly, I didn't face the issue when I performed an inplace upgrade on my Gen9 this past weekend from 2012r2. I was careful to install the Firmware and Driver using the HP SPP Package BEFORE proceeding with the upgrade. Instead of booting from it, I had to mount the .iso and initiate the SPP from the OS. This ensured that the server commenced driver installations rather than just focusing on Firmware. Post-upgrade, I did run into some problems with NW teaming. The inplace upgrade disrupted the teaming and prevented me from using the same pair of NICs to reestablish it. This might have been because the configuration was still partially lingering in the registry. Rather than troubleshooting, I simply used ports 3/4, the two other available ports, to set up a new teaming, and that seemed to do the trick.

Have you considered UiPath support parameter in this regard? Will there by UiPath support for window legacy issues after deprecation? I am yet to explore and gather knowledge on this front.
However, I did understand that we will still be able to run, edit and open windows legacy projects but there is no mention that if we run into any problems for legacy projects, support would be there or not.

But Legacy activities are offered e.g. within the UiPath.System.Acitvities. So we would assume as long the offered Package is in support (Version Level Details) we would get support from UiPath as ussually

My laptop has not offered the update to 22H2. The last update that I was offered and installed was 21H2 build 19044.2846. Up until now, I have been offered all the previous updates. I have been reading the other posts and noticed there are others like myself. Last night I visited the Microsoft site and downloaded the ISO file Windows 10 22H2 file which is 6GB in size. If I burn and install this file will I be able to accomplish my desire to upgrade to 22H2 and yet keep all of my installed software?