I upgraded my 2013 MSI laptop with 24H2, I had to do the 23H2 ISO fix. I downloaded a 23H2 ISO extracted it to the desktop, downloaded a 24H2 ISO extracted it to the desktop. Copied the install file from 24H2 ISO and switched it with 23H2 ISO, I had to change the extension to esd or something. I then went to GitHub and find a Windows 11 bypass dll file. Ran the setup and installed it. I couldn't install it using the 24H2 ISO, the bypass dll didn't work with that.
Works great, went from 23h2 to 24h2. However it took a few restarts before it started running smooth after the update. I am using the Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz .
Maybe it's because I had a triple-boot 2000 Dell desktop once (98se-2k-XP); but I don't look for trouble anymore. W10 and ESU or 0Patch for my 2012 Dell desktop.
I noticed 24h2 feels a bit snappier opening right click menus right away, i have dual boot, and 10 is using 2.4g of ram at idle and 24h2 is at 3.1g, so that would explain for snappier os.,problem is there are still 2x more clicks to get to things, right click to get the menu then select show more to see the rest of the menu i hate it .
Installed Windows 11 on my laptop with no cpu support for it. It installed just fine. My pc is only a test pc. Microsoft can close this way of doing it anytime they want to do that.
*UPDATE:* My machine has no TPM, Secure boot is disabled, my cpu is W11 compatible(Ryzen 7 1800X). I downloaded the official 24H2 64 bit ISO from Microsoft and used rufus to do a full install to my unsupported machine. I checked the boxes to disable checks for TPM, secure boot and Bitlocker. I'm up and running and I've installed basic updates (hardware etc). My current build is 26100.1742. I have not installed the Windows Insider update preview KB5043178 as of yet.
Strange thing happened to me yesterday. I wanted to do a clean install of 24h2. Made a thumbdrive with the media creation tool, restarted PC and the install procedure started, but arriving at the point where you can format your drives/partitions, the setup didn't recognize my C drive. Only de thumbdrive was listed... So I had to abort the operation and installed 24H2 from the thumbdrive while running 23H2... Any suggestions how this is possible?
Is BitLocker running on the unsupported computer with a clean install? How about Copilot? I have 24H2 on a supported machine I upgraded to from 23H2, just curious.
There is a reg modification that you need to run. Found over on git hub thru Rufus web site. Just ran into this on a unsupported pc today, now I got past the cpu, tpm and secure boot error message that stopped the first upgrade in place with 23H2 already installed. Was said they will add this modification to there program eventually.
Are there still reports of a clean install of Windows 11 24H2 running Bitlocker in the background ?. Just curious and can it be disabled ?. My experience of 24H2 which I recently updated to gave me just a few problems. First of all after the update a warning dialogue box appeared saying a " device driver cannot load on this device ENE.sys " yeah ok wasnt expecting that one. My belief is the ene.sys is something to do with RGB, probably left over from Asus Armoury Crate which I uninstalled a long, long time ago. Or some other RGB on my Motherboard .I stiil have a folder called ENE, with ene.exe lying in there, and 2 entries of ene.sys in Windows drivers and Program Files. I searched for ene.sys and just renamed the file to" ene.sys.old "to stop the dialogue box appearing. I will investigate ENE and remove those ene.sys files. This is the first time after scores of Windows 11 updates that i had this ENE.sys warning. Hmm strange. Maybe its just a placebo effect but also after 24H2 update there seems to be a very, very slight lagginess in Windows. Maybe lagginess is too strong a word !, but a certain less nippy system, overall. I dont see a huge difference with this update, nothing super special, that I could actually get excited about, a few things here and there, some good yes, but I was expecting more. More and more of these Microsoft upates are getting problematical, from the basic updates to feature updates etc.
