"Complex"? A 32 byte hex edit? ... ... ...Really? (And this is specifically for my netbook - upon which it runs perfectly. I know what I'm doing.)
Also make sure you only use Windows 8 x86 if absolutely necessary. If any of the following are true you should definitely be using x64: - a recent computer - a computer with more than 3GB of RAM (so you don't hit the 4GB limit) - a compute with a video card larger than 1GB - if your combined video RAM + system RAM is, or exceeds, 4GB - you have an SSD, in which case you should be looking at NO LESS THAN 6GB system RAM on i7-9xx, and 8GB on i3/i5/i7-2xxx/3xxx processors and AMD processors You shouldn't really have an x86 only processor if any of the above applies. The last item is so you don't necessitate too much writing to a pagefile on the SSD, which is not at all good for it.
Download xdelta3.0z.x86-32.exe from code.google.com/p/xdelta/downloads/list open Command Prompt and Enter commands Code: xdelta3.0z.x86-32.exe -d -s OldWZT.ISO DeltaPatch.xdelta NewMSDN.ISO
You need to replace the data with 0. If you remove the data or paste zero's you move all the other data's offsets. I would guess you are using WinHex, just search for the start of the data and type 0 over each byte and save. If you original files matches the ZWT# then it will match MSDN# if done correctly.
put (xdelta3+WZT2MSDN_WIN8PRO86.xdelta+zwt_pro_x86) on desktop then hold on shift key+right click empty area and choose open command window here then insert this command and hit Enter: Code: xdelta3.exe -d -s zwt_pro_x86.iso WZT2MSDN_WIN8PRO86.xdelta Windows_8_Pro_EN-US_x86.iso change the red colored name with the name of zwt iso
Windows 8 Enterprise N (x64) (English) Delta Patch !! Can anyone please upload the xdelta patch for Windows 8 Enterprise N (x64) (English) !!!
This makes no sense. If, by zeroing the "signature", we arrive at MSDN version, how can the MSDN version have the signature and the WZOR version doesn't? It's exactly the opposite, which is strange. Maybe the WZOR leak contains a fingerprint to trace the leak.
I thought that was a little strange too. But the WZOR release does have the fingerprint, the MSDN ISO doesn't (just 0x00) so that doesn't make sense .
One possible explanation is that Wzor also had access to other sources which had different 32 byte fingerprints. Having realized that those bytes indicate the source, he may have filled it with dummy data. And most on the scene probably knew about this, which is why Canouna had said that though the build was final, the MSDN hash might be different from the leaked one. In the final release MS may have just nulled the fingerprint, having no need for it.
Okay, I understand that the only difference between the leaked builds and MSDN iso is just 32-byte fingerprint. So, the presence or absence of this fingerprint should not no effect on Windows installation, activation and functions, right?
Man, can i just get a clear answer, i have the WZOR release activated with KMS, is there ANY NEED to reinstall the one that released yesterday on MSDN?.
WZOR or whoever has ONLY deleted the digital certificate info on file 'install.wim'. The contents itself have not changed. Chill mate, WZOR HAS leaked the real deal.