Cara Upgrade Windows 8 Ke 11

[Kayleigh Telega]

I have a windows PC running on windows 10. This PC is not connected to the internet. How can I upgrade node-red here? I can access the PC. I've been looking for a solution for a while, but can't really find it.

The PC is behind a remote control unit that closes the network from the internet via a firewall.
I use node red for visualization and communication with a PLC, which is also on that network. That I can access it remotely is for service purposes.
The version of node red that I am using now is v0.20.0.
I want to change the node node-red-contrib-mssql to node-red-contrib-mssql-plus.
For this I have to adjust the node-red dashboard. This gives a conflict with node-red-contrib-ftp causing the node red to crash. With the new node red v1.02, that seems to be going well.
I assume that the PC with node red must have an internet connection if you use the normal command npm install -g --unsafe-perm node-red.

There are several variations but simply put, you need to download the npm package to something like a memory stick. Then you need to install it from there. Of course, you also need all of the dependent packages. You can can use the package lock file to help with that.

I am running node red v0.20.0 on a virtual machine without internet connection in a production environment to investigate machine data acquisition via OPC UA.
I want to update node red and several nodes to the latest version, because I am not able to connect to a MS SQL database (but that's another issue...)

@TotallyInformation - You proposed to copy & paste folders from a second PC to the destination system. After doing so, what would be the next step?
Exceute npm install -g --unsafe-perm node-red as advised in the Getting Started section or will it work out of the box?

From your post above, I assume that you have established a connection between a MS SQL database and node red using the node-red-contrib-mssql (-plus) package(s). May I ask, if your DB runs on the same machine like the node red installation? Did you face any troubles setting up the connection?
Somehow I am not able to login to a database on a different server using Windows authentication. After searching the forum and trying many things, I am still stuck somehow and hoping that an update may improve the situation...

Note, however, that if you installed Node-RED using the default -g method, you now have two locations you need to copy from. One is the global install library (you'll have to look up where that is, I can never remember) and your userDir folder. If you used my alternative installer approach, you only have a single master folder to copy (but it is likely to be BIG).

My dBase is indeed running on the same PC. I log in with a user name and password.
I have to open the ports on the PCs (firewall)?
SQL, TCP 1433
The following settings in SQL Server Configuration Manager

I'm currently testing out Windows 11 upgrades for an Enterprise environment and have run into a ton of issues. I discovered that our 3rd party anti-virus was causing conflicts, however even on clients with that removed I am seeing intermittent failures when attempting the upgrade from Windows 10 22H2 to Windows 11 23H2.

Attached are some of the resulting files from running setupdiag on one of the computers that has failed the update. If anyone could provide insight into what could be causing the issue, I'd be very appreciative. I've seen tons of different errors in tons of different places and have no idea which ones are actually causing issues and which ones I can ignore. I've seen similar problems on numerous different models of computers but they are all Dell in case that is relevant.

have you tried using the windows 11 upgrade assistant / Windows 11 Installation Assistant?
I have seen this issue in the past and using the Windows 11 Installation Assistant fixed the issue a few times in my case.

Thank you for your suggestion. I have tried booting into a clean environment and then running the upgrade and that didn't seem to make a difference either. When I tried that though, I tried installing Windows 11 through the Upgrade Assistant and not an .ISO file. I have tried an .ISO install outside of a clean boot and that did not seem to make a difference either.

I don't know where to go from here really. I'll keep going through logs and seeing what I can find but I'm running out of ideas. The main error code I'm seeing is 0x8007042B-0x4000D and the problem is almost certainly a migration error, however I don't believe it is driver or local profile related as I've updated all drivers and there is almost no user data on this computer.

I have been using the .ISO file. The install.wim file is custom as I extracted a version that only contains the version of Windows I'm looking to install. I couldn't get the ISO to work and switched to manually attempting the update via Windows Update or the Upgrade Assistant and got the same 0x8007042B-0x4000D error no matter what method I used.

But why should companies consider upgrading their operating systems when the one currently in place works just fine? That might be true at this moment, however, there are benefits to upgrading operating systems. Here are a few:

Create a new Windows Update Ring specifically for the Windows 11 upgrade, assign a name to help easily identify the feature update deployment, and then give it a description to help give the policy some context. Under the Feature deployment settings, set the version of windows you want to deploy next to Feature update to deploy. Once your option is selected, next select the Rollout options to manage when you want this update available.

With Windows 10, Microsoft switched to a rapid release model for the Windows operating system. That means that Microsoft releases a major "service pack" for Windows 10 twice a year. These are sizable updates that add or change major features in the Windows 10 operating system. The IT Department restricts them coming through our Windows update system in order to give us time to thoroughly test these substantial updates before rolling them out to campus. When it is time for your computer to receive the update, your Computing Coordinator will contact you.

If you did not come to this article because your Computing Coordinator asked you to install the latest Windows 10 version, then please STOP and check with your Computing Coordinator before proceeding! Although this upgrade process is non-destructive to your data, it may significantly change Windows or break the functionality of certain programs.

Be advised that the update process can take upwards of one hour. You can continue to work while the update installs for part of the process, but please avoid working in documents that need to be saved because you will not receive much of a warning before the computer reboots.

If you want to verify that the update completed, we recommend that note your version of Windows 10 before the update and then check it again after the update. If the version number changed, then your update completed successfully.

Follow these instructions if you are using a SOU-issued Windows computer while on the SOU campus. If you are not using a SOU-issued computer, or if you are not currently on-campus, then follow the instructions in the next section to get the update directly from Microsoft.

Click on Operating Systems in the list of links on the left side of the Software Center window, then select the Win10 Upgrade item in the apps list. It should be the only item there.

You should see the following progress window as the update installs. It can take upwards of 45 minutes for this window to go away, then your computer will reboot several times to finish the upgrade, which can take another 15 minutes or longer.

If you are off-campus or using a personal Windows device, you can update to the latest version of Windows 10 directly from Microsoft by visiting -us/software-download/windows10. Click the Update now button on that webpage to begin.

Download the upgrade assistant program and then run it. It should launch itself after it is done installing, and it will leave a shortcut on your desktop and in your list of all programs that you can use to launch it later.

The update assistant will check your system for compatibility with the latest version of Windows 10. If it passes, you can click Next to continue. If it does not pass, contact your Computing Coordinator for assistance.

Eventually your computer will reboot in order to finish installing the new version of Windows 10. That final step can take 15 minutes or longer depending on your hardware. Please be patient while it finishes. When the update finishes, log back in to Windows as you normally would.

c80f0f1006