...I am here to tell everyone here that the widely available copy of Build 4011 is apparently a corrupted one, because first, when I try to boot from it, all I get is an error message (the same happened with Build 4008, but at least I was able to install it from another Windows installation).

Since I got the message "There was an error copying files" from trying to install it from Build 4008, I decided to once again try to install the later Longhorn build from Build 3718 (I did the same with Build 4008, and the installation was successful), only to receive the same error message.

The error occurs while trying to copy files for WinPE, so presumably, it's just the WinPE that is at fault. Hopefully someone can repack the build so that the files copy properly (most likely maxtorix or linuxlove will be the ones to do this), since that is the only way to install it successfully (most likely, the screenshots of this build seen are of copies that were repacked so that the files would copy properly).

WinPC, this is an endless topic, there are many like this. The BA one is corrupted, you gotta got it working yourself, just a suggestion, ask hounsell for 4011 from his FTP.

put 4011's install.wim on 4008.

Or use Pwned's Longhorn packet.

cassiodoroVicinetti already reported this.
Also, this is the nature of leaks, some come here untouched, and some don't.
You'd better bear with it.

I'm sorry, but I tried exactly that, and not only did it NOT work, but I got the EXACT SAME error message.

I did exactly that - I copied the files from Build 4011's .ISO image into C:\LONGSET, I copied the files from Build 4008's .ISO image into C:\LONGSET2, I ran Longhorn Setup from C:\LONGSET2, and I receive the same message.

Long story short: The build is completely destroyed, nothing can be done to fix it unless we were to extract the .WIM files themselves and completely repack the INSTALL.WIM file (that file is apparently what is at fault, and nothing else, contrary to "popular belief").

And how do you know that for a fact, the BA copy is corrupt and that hounsell has a working copy on his FTP server? Hmm...

Yup, CaptainPeanut got it, some are untouched, some come corrupted.

WinPC, I saw hounsell is on, send him a PM to message you M1 FTP details. I heard there is the working 4011, that is the one that still needs to be put in 4008, but the copying files error does not occur.

@linuxlove I saw that somewhere ages ago.
-W4E

linuxlove, since you're here, do you know of working repacks of this build? Using the Build 4008 installer does not work at all - apparently, the files within INSTALL.WIM are damaged, and the only way to repair it is by extracting the files from the .WIM itself and creating a new one.

Also, Pwned's "Longhorn Packet" would require downloading all of the pre-reset Longhorn builds, since they've all been packed into a single installer, and I don't have the space for all of that (not everyone has dual 500 GB hard drives you know, no offence).

I do have an older version of LH packet, just working fine with e.g. 4039, no need to download all, should I PM you a link to it?

Sorry, I have no idea where you can find a working copy of 4011 these days, that is, if you can still find a copy.

Yes, I reported this here.


No, the problem is: the 4011 wim file is corrupted.


I have a working copy of 4011 iso. Some time ago I uploaded the wim file: see if these links still work, otherwise I'll reupload them.

EDIT: Mistyping 4008 -> 4011

Out of interest, what's the MD5 of the corrupted ISO?

Can someone else try out this particular copy of the INSTALL.WIM file, just to see if it works?

Also, why is the archive divided? Is it a spanned archive?

Finally, if it does work, then I'll gladly repack the build and rerelease it here for everyone on BetaArchive. I'll also be sure to reupload it, with a notice for mrpijey.

Right MD5: 4d1a03c7e724e6b5bd4ff5d7b8dcc119
Wrong MD5 (corrupted): 82ab0fa174ed2de327dce1083dbbb336


It comes from the uncorrupted iso: I installed 4011 successfully by copying this wim to 4008 iso.


It is a multivolume archive that I made with ZipGenius, because:
1) my Internet connection is very slow;
2) I couldn't upload files larger than 200 MB to MediaFire.


I have the full untouched ISO. Should I try to upload the whole iso (my connection is slow -> it will take a lot of time again, and I have to split it into small pieces)? Better to MediaFire or to FTP upload (see below)?


Some months ago I uploaded this iso to FTP, along many other isos that aren't in the FTP*, and I sent a private message to mrpijey explaining why I uploaded these things. mrpijey did not reply to my message, and he deleted my files from the upload FTP without moving them in the download FTP, maybe because they weren't rar archives but they were multivolume zip archives (remember my connection is slow...).

* What I uploaded in vain:
Microsoft Windows Vista (''Longhorn'' 6.0.4011.0) (beta)
Microsoft Windows 95C (4.03.1216) (OSR2.5) [Italian]
Microsoft Windows 98 (4.10.1998) [Italian]
Microsoft Windows 98 Second Edition (4.10.2222) [Italian]
Microsoft Windows 2000 Professional (5.00.2195 Service Pack 1) [Italian]
Microsoft Windows ME (4.90.3000) [Italian]

Good, all my copies are the good version

Good, same here

Edit: From the .nfo:
OSBetaArchive.com
It is confirmed working and has been tested on virtual and real machines.

So I can avoid uploading my copy.

I created a PAR2 file based on the good Install.wim and tested it on a corrupt copy of Install.wim. Seems to fix it real good, so if you've already got the corrupted version, you can apply it to your file to gain a fixed copy. You'll need QuickPAR or some other par2-compatible application to fix the file. Download: http://www.jimmsta.com/lh/4011_InstallWIM_PAR2.zip

I have a corrupted iso, of which the MD5 is exactly the wrong one. I'll check this when I have time and tell if it works.

Maybe I won't have to spend hours to re-download the whole iso if I fixed it.

It will take a lot of time (mostly uploading), but I will try to fix the 4011 setup and replace the incorrect WIM with the correct one for you guys, If is anybody interested PM me. When I am bored, I repair ISO's most of time

Tested the par2 fix, and it finally got to work.

At first I replaced the fixed install.wim into corrupted 4011 iso with Magic ISO, but I got BSOD when bootup. Then I used UltraISO, with assertion error, which also exists in the "untouched" corrupt one.


Last I put the fixed wim into 4008 iso and finished installation, despite it remained blackscreen at the last step and I had to reset.


The bad install.wim has got the following hashes:


And after I fixed with QuickPAR, hashes of wim changed to the following:


Eventually with this fixed I can accomplish the installation, yet can someone tell me the hashes of the wim in the good version?

So, the problems with 4011 iso should be:
     1. The wim file is corrupted. This should be fixed and/or replaced.
     2. The installer is damaged as well. Setup will not continue due to a debug assertion error message. Thus I have to use the 4008 media for alternative.
Is that correct?



That would be great. Though I have fixed the wim, I moded the iso with UltraISO. I still want the original good version of iso yet.

You can definitely fix the "Debug Assertion Failed" error with Longhorn Packet (and the installer will be the original version 4011, not 4008), and this error would come up anyway, doesn't matter if INSTALL.WIM is corrupted or not.

That's my fault, sorry...

I didn't realize it is designed to fix that problem. Anyways, thanks for your tip.

PlyrStar, If I don't count LH Packet as solution (it is a solution anyways), the bugs you mentioned are right, anybody, when you'll see a longhorn icon in my signature, it's the 4011 repack , working on it now.