dencorso

The more, the merrier!

It sure isn't a coincidence April 2019 is also POSReady 2009's EoS.

Have you ever read the Rules? Are you sure? 7d and 8 ring any bells? Since you've made it public, consider yourself warned.

The safest place to get the files you need is %windir\Driver Cache\i386\ and a second copy of them ought to be in %windir\system32\dllcache\. Then: from Safe Mode or a Recovery CD: go to c:\windows\system32 backup hal.dll, ntoskrnl.exe and ntkrnlpa.exe. copy dllcache\ntkrnlmp.exe to ntoskrnl.exe copy dllcache\ntkrpamp.exe to ntkrnlpa.exe copy halmacpi.dll to hal.dll; reboot.

It seems the new kernel requires VT-x, even for x86 versions... but I've not yet found a reliable source for this info, just hearsay... sorry!

Try instead: Reboot. After the hal and kernel get replaced (i.e.: on next reboot), replace by your previous boot.ini, but you may omit the "/ numproc = 4"

Hi, Petr! It's good to hear from you! I imagine it's the lack of processor support for some instruction that wasn't required before and now suddenly became mandatory. In case I'm right, it's happened before, not so long ago, on the transition from 8 to 8.1... It may simply be that they've given the next mini-step and are now refusing processors not supporting x86-64 mode even when installing a x86 version of Win 10. Of course it's nonsense to require x86-64 support to run in x86 mode only, but MS stopped trying to make sense long ago, so it'd not surprise me if this guess turns out to be right. ==== Another possibility (albeit less probable, IMO) is some artificial block like the one described and bypassed in this beautiful project elsewhere. Of course, any of the above are just my best guesses, I have not performed any tests nor read anything about it prior to your post... and YMMV.

You bet! @heinoganda does rock!

Because one can! It's bad netiquette on MSFN to ask such a question... I'd imagine that, at 400, posts you'd know that by now...

OK. But read my previous post 1st. I guess I just found the answer you sought...

Then again, perhaps my google-fu still works somewhat:

Ah! So it's not our site at all! Why don't you PM @tomasz86 or @blackwingcat, instead of posting? It may take some time, but sure shall give you better results. I'd help you myself, but I fear in this case I'm unable to, except by the advice I've just given you. Good luck!

Whoose site? Which site?

Done.

I, however, would be damn utterly flabbergasted!

And you're right: the one and only speu20.exe (1999) is the one linked to by @MrMateczko: Now, the OP may as well keep on a wild goose chase for as long as he likes. The sought-after help, however, has already been given.

* Turn up the sound! *

+1

We do, too! Ours're smaller but tastier, since they come full to the brim of schistosomes...

No empezarás discusiones sino que en Inglés! [Don't start threads other than in English!]

@rloew: Read this: http://reboot.pro/topic/21812-community-ofa-nvme-15-storport-miniport-for-windows-server-2003-r2-sp2/ I've had no success at all with it, though, either on my P8Z68-V LX or on my H67MA-E35 B3, each powered by a 3770K i7, with either a 250GB Samsung 360 EVO or a 370 EVO. BTW, the very latest extant storport.sys (v. 5.2.3790.4485) is findable inside WindowsServer2003-KB957910-x86-ENU.exe

+1 Don't create a fuss where there isn't any. Preserve @roytam1's work for those who need it (=us).

Ever heard of fcwin2k? Then again, there are other ways, too...

I confirm the problem has been solved: the oleaut32.dll from KB4466388 is good, according to my testing.