Leaderboard

Will publish a customized MSE Updater, but this means that the mpengine.dll would remain at the state of version 1.1.15800.1. A test with the Eicar test virus has been positive with the most recent virus definition. In how far this will affect more recent virus definitions in the future, I can not foresee. The fact is that in future vulnerabilities or functional extensions in the file mpengine.dll no update is possible. There are still some tests needed in the next few hours and if they go well I will publish the updated MSE Updater.

@ Deomsh & Dave-H. I've been following your work here and finally got some time to give HDA a try on my Dell Inspiron 9400. It has Sigmatel 9200 audio. I followed pg1 of this topic instructions. The driver loaded and I could see HDA in the multimedia sound options however I got a BSOD with an "application error" when desktop loaded but was able to continue-no sounds heard. I then copied HDAICOUT.HDA to my Windows directory and on reboot heard 2 pop sounds- but still got the BSOD. Then I added the minfilecache,maxfilecache=8192 and rebooted. No more BSOD and the Welcome sound played at full volume. I grinned like a kid at Christmas at this point. That's all I have time for today, but thanks for all your hard work. I'll try to look into the volume control another time as I read you got that working.

Poor quality photo this time, but at least original content - XP booting in Warsaw suburban train Not sure if pure one or embedded. Photo from today's morning.

I think a batch file like this will get me by for a few days: @echo off net stop MsMpSvc echo Please ignore "At Risk" pop-up from Microsoft Security Essentials while the latest definitions are being installed cd %TEMP% if not exist mpam-fe.exe "%ProgramFiles%\HTTPSProxy\wget.exe" -O mpam-fe.exe http://go.microsoft.com/fwlink/^?LinkID=121721^&clcid=0x409^&arch=x86^&eng=0.0.0.0^&avdelta=0.0.0.0^&asdelta=0.0.0.0^&prod=EDB4FA23-53B8-4AFA-8C5D-99752CCA7094 cd "C:\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\Updates" "%ProgramFiles%\7-zip\7z.exe" x -y "%TEMP%\mpam-fe.exe" *.vdm del "%TEMP%\mpam-fe.exe" net start MsMpSvc 7-Zip and wget required. Note: this is specific to my system; you'll probably need to adjust some path names, depending on where 7-Zip and wget live on your own systems.

It should be "true." However, with FF 52, it won't do anything unless you add some custom Javascript:

No. It's not just maybe. Here're some facts... This is the ominous line in dependency walker: Notice it's an error, not a warning. Moreover, it appears for 1.1.15900.4, but not for 1.1.15800.1 or any other previous version of mpengine.dll (I've tested two more, but that should be enough, in this case). So, MS's attempt to kill XP through MSE lies on the mpengine.dll... That's good news! I count on @heinoganda kindly creating an automated updater, from these findings, as soon as he finds time for it, of course!

I tried copying the engine version from my Windows 10 installation, which is version 1.1.15900.4, to the MSE folder, and what happened was that when MSE restarted, it restored the original version, and the old definition files! When I just replace the definition files it seems to be fine, so beware trying to update the engine version!

I confirm it works: 1.) stop MS Antimalware Service ; 2.) put the 4 .vdm files in "C:\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\Updates"; 3.) restart MS Antimalware Service; MSE updates and the "...\Microsoft Antimalware\Definition Updates\Updates" becomes empty. Great work, folks! Y'all rock!

I did it a little different, tried something else stopped antimalware then copied files to update folder instead, (which it let me do) started antimalware again and it updated its a work around, but at least it works for now, even if it is a bit a faffing about

It is a "forma mentis" of many years of IT Security work. Thank you for your interest.

OK, here is the log. I am running Windows 10, not Vista:

@click-click These are just the GUI options on the Ready? GUI. The last 3 should be 0 or 1. You just add all options in the WinNTSetup.ini there is no wimlib.ini. @SteveSi On XP Tab you need to right click on the source button to select an ISO.

Well first make sure the installation has the wof driver installed. Best if you have installed that system with any of WinNTSetups compact option. Than start the compression: WofCompress -c:LZX -path:C:\ It will automatically use the exclusion list in WimBootReCompress.ini that WinNTSetup has placed in Windows\System32 folder. You can also use it to just compress any folder, if you want: WofCompress -c:LZX -a -path:D:\Programs

For what its worth, the .exe installers function just fine on XP x64 edtion/Server 2003 http://prntscr.com/nfv7qn (note: I believe this installer screenshot is from around the 8u170-era but i can confirm that it still works.)

You are right. I can confirm that something is indeed very wrong. I would actually say that this is a critical bug. I am pulling the FullPack from the download Archive for now. I will have to test whether it is another component butchering the installation, or HFSIP2000 itself. I am very sorry for the situation. I am not using Windows 2000 as my daily OS anymore, and no one had reported these problems before, so I had no clue. I will try to find a solution as soon as possible.

If you love XP just use it in a VM like Virtual Box. I do this to run old programs frequently.