Recent content by hugosimoes

It means... computers with core 2 duo and core 2 quad, less than this generation (and maybe the generation after this one, socket 1366) will not work with Build 25905. If you have such machine and you attempt to boot the ISO from a pendrive/dvd or load an restored image from ssd/hdd, an Windows...

News? Yes and no. I was wandering on the interwebs and found a French forum. Well... all over the net they are rumbling about same problem: MS will be forcing users to leave old-ancient platforms. In the forum, some user did a experiment with xeon and turion and these 2 failed except with hp...

Well, I can confirm that trick works. I once did that to install a build. I think it was when build 22000 was out. I observed Resources Monitor to check where the files were being downloaded and extracted and I able to quickly replace the dlls to get past that 8-10%.. basically the error dialog...

I know that the expire date is about to kaboom. No viable workaround yet. I started a new topic at MDL under the name "Dangers of builds 25905+" but... nothing yet. Maybe you want to ask there also. Just stupid that MS added a Pro SKU when the target is a Windows Server platform. We are now...

Builds 25905 onwards are allergic to unsupported PCs.

And I kinda confirm it... Windows ... 11 ... builds 259xx+ are allergic to something old... I setup a new vm... EFI off... and used some ISO for 22621 because I deleted 235xx from hdd... I booted with that ISO and used Shift+F10 and created a single partition of mbr style and formatted. Then...

Well... I just compiled a fresh ISO with build 25921. I downloaded the latest Rufus 4.2. I ran Rufus, selected the ISO, left the defaults to remove the 4gb, secure boot, and tpm 2.0.... and created a usb flash installation. I hooked the usb pendrive to the mini PC... Alfawise X5... bought years...

Hi jimbo. I am using Oracle Virtualbox on Windows. I probably forgot to mention. I can create a new virtual machine, load the ISO, yada... skip unattented, new virtual disk. If I load ISO with build <=22631, 234xx/235xx, or 253xx, the VM reads the ISO (boot.wim into memory, the spinning circle...

Hah... Sunday... Yet to move from 25393.... The 259xx simply don't seem to like old machines at all. I tried Rufus and create a usb flash install... even a vm... The boot.wim seems to load into memory and then we never see the spinning circle.... unlike with 234xx/235xx. By tradition, we can't...

An installation taking so long is not really normal. I don't remember it taking that much. It usually took upto 2 hours when I used an slow hard drive ages ago. Seeing 23493 and 25905, it doesn't seem nothing much happens under the wood. If I had 23493, I would use dism ... /scanhealth...

Well your hardware is newer than mine. But something preventing the Windows PE from initialiazing.

Not able to upgrade yet. I built build 25905 from uup which generated an ISO file. I generated an usb flash with Rufus and used a laptop running 25393... which failed after first reboot.. it simply froze with the Windows 11 logo and no spinning thing. I also did the same on another laptop which...

Thanks for the reply. I thought so. The thing is that.. there is pro/home editions for build 25393 and not (yet) for build 25398. Microsoft is just playing with build numbers and making things confusing. I have built ISO for build 25398.287 but there are only 2 editions. I still have time...

Hi, I am new here but once in a while I come here and read some topics when needed. Back events: I am Windows Insider member since it's release. I been using/testing builds since the launch, even got my installation bricked at least once. I did "stop" installing new builds once I moved my...