Windows 11

[scarface]

Note that a new version of windows 11 is available here: https://mega.nz/folder/hFMVTIBL#OP7Z1vb95a0AIFl5-_UctQ

[humbert]

Note that a new version of windows 11 is available here: https://mega.nz/folder/hFMVTIBL#OP7Z1vb95a0AIFl5-_UctQ

Is this thing pre-activated? Is it amended so you won't have to forcibly create Micro$haft account? Did you remove bloat or add bloat, or both?

I'm planning to upgrade my rig later on and I need a fresh install. Maybe I'll use this copy.

[scarface]

Well, I think you should test this in Vmware to ensure it is suitable for you. It is not required to have an account if you select your username and input your password.

[Vasudev]

Updated Windows 10 Feb 2025
ISO: Win 10 22H2 x64
SHA256 Hash: https://mega.nz/file/pZgymBhQ#Xa7JnWb9uRAhTBcV4_3v4q1fmsUDb0aJXDDUWVz3dJs

[humbert]

Updated Windows 10 Feb 2025

I'm surprised you're still playing around with Windows 10. Isn't end of support not too far off? Does W10 even support newer hardware?

[Vasudev]

Updated Windows 10 Feb 2025

I'm surprised you're still playing around with Windows 10. Isn't end of support not too far off? Does W10 even support newer hardware?

Doesn't work on my new laptop but still in use on my 2 old laptops.

[humbert]

 I upgraded my desktop today and put 23H2 in it. Today from Windows Update came the offer to install 24H2 so I tried it out. What a disaster! Just for starters, my mapped network drives disappeared and there was no way to put them back. All I got was some sort of unusual password prompts that 22H2 nor 23H2 ever produced.

To make matters worse, the backup file I made would not restore. Macrium said it was "corrupt". The funny thing is that you could still map that backup to a drive and extract files. I had to start the configuration from scratch.
Stay away from 24H2 until they fix it.

[scarface]

I upgraded my desktop today and put 23H2 in it. Today from Windows Update came the offer to install 24H2 so I tried it out. What a disaster! Just for starters, my mapped network drives disappeared and there was no way to put them back. All I got was some sort of unusual password prompts that 22H2 nor 23H2 ever produced.

To make matters worse, the backup file I made would not restore. Macrium said it was "corrupt". The funny thing is that you could still map that backup to a drive and extract files. I had to start the configuration from scratch.
Stay away from 24H2 until they fix it.

I will upload a new version of windows 24H2 next week. Maybe you could install it in case you need it.

[humbert]

I will upload a new version of windows 24H2 next week. Maybe you could install it in case you need it.

I have a portable drive hooked up to my router's USB port. It serves as my personal cloud. I can access it from all my devices and anywhere else with an internet connection. With 22H2 and 23H2, you can easily go into Windows Explorer, click on "Map Network Drive" and put (in my case) \\RT-BEU92\sda1 and off you go, it's mapped as drive Z. With 24H2 this is impossible. You run into a wall of security where it demands all kinds of passwords and setting and all kinds of unnecessary requirements not even Microsoft understands.

Another problem that the activation from 23H2 was not grandfathered in. Reactivation was necessary. I only imagined that this was the beginning of endless problem with this badly written piece of garbage. So I decided just to screw this and go back to 23H2, which performs flawlessly. Let them fix it first. I might add that I've had infinitely more problems with security protocols than whatever it is they're trying to protect me from.

Have you tried to map a network drive on this thing? Is that even possible inside a virtual machine?

[scarface]

Have you tried to map a network drive on this thing? Is that even possible inside a virtual machine?

I don't use this feature so I won't be of any help...