win32

@Dylan Cruz This is the working procedure: 1. rename the crypt32.dll from the XP update to crypt33.dll and copy to system32. 2. Use Replacer to replace BWC's rsaenh.dll, schannel.dll and dssenh.dll with the one from the other XP hotfix. 3. hex edit MSO.DLL to point to crypt33.dll instead of crypt32. So BWC's crypt32 stays, but XP's is copied under a different name, and the three other BWC files are replaced. This outcome satisfies Word and Outlook at the same time. No need to modify any Outlook files.

@Dylan Cruz Oddly enough, even the changing of pointer to crypt33.dll in MSO.DLL doesn't change much for an Office 2007-encrypted file; as rsaenh.dll still calls crypt32. So I decided to just replace rsaenh.dll, schannel.dll, dssenh.dll. After that, mso.dll called crypt33.dll to successfully open the Word 2016 encrypted file, whilst outlook called the original crypt32.dll and connected to Yandex.

@Dylan Cruz I get the constant reappearing login window. But I did use dependency walker to look at the decryption process. WWLIB.DLL calls MSO.DLL (in Program Files/Common Files/Microsoft Shared/OFFICE12), which in turn calls CRYPT32.DLL which then calls advapi32.dll. That's at the start of the process. The rest of it is detailed in this dependency walker file who anyone who is interested. But I think the part I described is the most important. This routine seems to be shared by most of MS Office, but maybe not Outlook. worddecrpytionprocess.7z

@Dylan Cruz I thought the configuration had worked, but apparently not. And winword.exe doesn't refer to crypt32.dll either.

@Dylan Cruz outlook.exe is not calling crypt32.dll, but credui.dll is. The mso.dll thing isn't very important though. There are several other DLLs that serve its purpose. So I copied credui.dll, renamed it credu1.dll, changed crypt32 reference to crypt33, then changed Outlook's reference to credui to credu1. It's a system file as opposed to an Outlook library so doing otherwise could break Word encryption again. OR, we just keep everything as-is, and only have word refer to crypt33 (which would be the "new" crypt32). Outlook and all other software could continue to refer to BWC's files without hex editing or stubs. Or not, because I got IMAP sign-in working (Yandex) with credu1.dll.

@Dylan Cruz If it can't come to grips with our new crypt32.dll, I've got a new radical plan. Try hex editing outlook.exe (or whatever the execuatable is called) and replacing any pointers to crypt32.dll with crypt33.dll, Then take BWC's crypt32.dll, rename it to crypt33.dll, and copy it into system32. If outlook.exe does not have any references to crypt32.dll, it may be in one of the main program DLLs.

@Dylan Cruz Have you checked the file in system32 if its attributes match up with the one from XP? It has worked for me, but I've only used it to replace individual files at a time (I didn't use this method to replace the files in my VM last night though) But once you've rebooted, are you able to replace another file?

@Dylan Cruz You don't use 7zip to extract those files. You run them the update files at the command prompt with the /extract switch. A window will pop up asking where to put the files, and then the applicable files will appear in the "SP3QFE" folder contained within the one you created.

@Dylan Cruz Any kind of Linux Live CD would be fit for purpose. But there's also something called "Replacer" (http://www3.telus.net/_/replacer/) that will allow you to replace the files from within Windows. Replace all four using this method then reboot. The regular XP update is just as valid for purpose as the POSReady one. Have you tried reinstalling WMP 9?

@Dylan Cruz Oh yes, I forgot to mention that I replaced crypt32.dll with the latest one from POSReady. You'll have to do that when the OS is not booted though. EDIT: Oh wait, it was more than that. Other files from the aformentioned SHA256 POSReady update as well. dssenh.dll rsaenh.dll schannel.dll The last three files can be extracted from KB3081320 for POSReady 2009 from the Windows Update Catalog (using /extract switch at CMD); will look up the origin of crypt32.dll (5.131.2600.6459) update: turns out crypt32.dll can be obtained from KB2868626.

@Dylan Cruz The Office 2016 document opened when Word was tricked into thinking it was on XP!

@Dylan Cruz Unfortunately it didn't open in 2000 with Word 2007. As your document is using more modern Word features, it may fare better in WPS.

@Dylan Cruz Nice! Are the crashes random or are they occurring when a certain action is performed? Anyway, I tried the encrypted Word 2016 (AES-256 + CBC) document in Word 2007 SP3 on XP and it opened there. But an encrypted Word 2007 SP3 document created on XP opened in 2000 as well. I briefly thought that the issues may lie at the OS level after all; AES-256 support was added to XP through POS update KB3081320. But HFSLIP/BWC's have already incorporated the applicable versions of the files into win2k, and WPS works fine with them. M$ software being M$ software... Luckily WPS Office 2016 easily coexists with Office 2007. I've needed it to display a "super-modern" PPT file that 2007 couldn't, but bear in mind WPS has no support for Office 95 files and has issues with 97-2003 ones.

@Dylan Cruz Then remove this line as well: if "%OS_SP_TARGET_ID%"=="" goto NoSPTargetId

@Dylan Cruz I honestly don't know why, but I end up using New Moon often as well. For the codec issue, have you tried a reinstall of WMP 9? Since it seems broken enough for visualizations to be completely borked, you may as well do that.

@Dylan Cruz Yeah, the visualizations in WMP9 do work for me. They should only not work with MIDI/RMI files. And try removing this from DoUpdate.cmd :NoSPTargetId echo. echo ERROR: Environment variable OS_SP_TARGET_ID not set. echo %DATE% %TIME% - Error: Environment variable OS_SP_TARGET_ID not set>>%UPDATE_LOGFILE% echo. goto Cleanup

@Dylan Cruz I found a possible solution for WSUS. In the "cmd" folder, open DoUpdate.cmd in notepad then find and delete the following lines: rem *** Check Operating System *** if "%OS_NAME%"=="" goto UnsupOS if "%OS_NAME%"=="w2k" goto UnsupOS for %%i in (x86 x64) do (if /i "%OS_ARCH%"=="%%i" goto ValidArch) goto UnsupArch :ValidArch Never heard of that Chromium version, but I'd be quite shocked that it can't do HTTPS. New Moon will give you that 2000s browser look for sure.

@Dylan Cruz On the right sidebar of the WSUS site, below the "ESR version" heading, version 9.2.6 is listed. It won't load unless it thinks it's on XP though. The mp4 thing is still odd, considering that I just played an mp4 file in MPC-HC 1.7.5, VLC 3.0.0 and WMP 9 with the K-Lite Codec Pack (if you want the safe, crap-free download I used, go here: http://www.codecguide.com/download_kl_old.htm#xp_last_version) I don't exactly know if an option exists in VLC setup, but if there was one for codecs, did you select it? And I was also able to run the VLC uninstaller.

Did you download from the "version 9.2.6" or "version 11.8.3" link? Download version 9.2.6. It will give you options for Office 2007 and 2003. Yeah, probably not. That version doesn't even work natively on XP - it targets Vista and up. 3.8.0 is the last XP compatible version; maybe that could work with the APIs you do have. And I'm actually not sure if I had 7zip 19 installed before extended kernel. But v16 isn't radically different.

@Dylan Cruz Try WSUS Offline Update ESR version (http://download.wsusoffline.net/) to download/install your Office updates. The Windows 2000 High Encryption Pack provides 128-bit encryption to Internet Explorer and similar MS applications I believe; necessary for online banking. It doesn't have any bearing on the encryption techniques used in newer versions of Office; especially since WPS doesn't mind opening it. The "high encryption pack" for Office mentioned in that error message doesn't seem to exist, or it was probably only released to certain corporate customers. VLC 3.0.6 and up are broken on win2k presently (can't play videos), but 3.0.0 and maybe a few newer than that are functional. And this basically says that FileZilla 3.25.1 works, and maybe even a newer release since that was posted 2.5 years ago. 7zip 19 continues to work on vanilla win2k. I just realized that we steered badly off-topic, then went back on-topic for a bit, just to derail it again.

You probably saved the document in Word 2010 or newer, which effectively made the encrypted document incompatible with 2007. Installing all updates to EOS for Office 2007 may help though. I think Microsoft Update still works and if not, there is WSUS Offline Update. The high encryption pack is integrated into the OS with SP2 and above. Before that, it was supplied on a floppy disk separate from the OS due to the U.S. cryptography export laws. The HFSLIP files. I believe that the new version can work, with one of the conditions I mentioned above, but otherwise it's a little ropey. I don't have any mkv files to test though, but I remember doing so in VLC 3.0.x at one time. Have you tried the K-Lite Codec Pack 13.8.5? That claims to better support MKV than VLC, and it works with WMP on W2K.

OK, I made an encrypted document in Word 2016 and got the same message as you did when I tried to open it in 2007. I think it has to do with the fact that encryption methods change with almost every Office version. WPS Office 2016 did open that file though. And on another note @Dylan Cruz, you don't need to download USP 5.1, as you can obtain a good copy of riched20.dll from the slipstreamed install media. Installing the extended kernel twice with DX10 option unchecked (with it checked, it was only necessary to install once) will (usually) allow for the "Windows 2000 Power Pack" start menu folder to appear with fcwin2k, NNN4NT5 etc. Apparently if it's installed thrice it will eliminate riched20.dll's VC++ 2008 dependency issue, but I've yet to test it.

That's also weird. I just installed SP3 (which needs 1.5 GB of HDD space by the way). It's greyed out in add/remove programs, but Office 2007 itself is not. It was specified as such in the "about" box; I was able to use several features introduced in SP2/3, including PDF exportation. I also created an encrypted Word document, which I was able to open successfully afterwards.

Yeah, New Moon's UI is the same as Pale Moon. That msvcr90.dll dialog can be fixed by replacing riched20.dll in system32 with the one from your Windows 2000 ISO (which will appear there as riched20.dl_; extract with 7zip). I think that should help you with your product key situation, given that riched20.dll is the backbone of the OS' Rich Text Format engine. That's used to display EULAs in Windows installers, so I wouldn't be surprised if it had something to do with product keys as well. I've never seen the "DDE Server" window though. It's probably linked to the riched20.dll/msvcr90.dll issues.

I'm not sure where to get Chrome 49, but yes Serpent 52 only offers the same Australis interface as Firefox 52. In terms of updates it actually corresponds to the official Moonchild product for Win7+, Basilisk 52, which is still updated regularly so it's far past 52 ESR. New Moon is again, much more advanced than the last official Pale Moon release for XP (extended win2000). Both New Moon 28 and Serpent 52 do video playback on YouTube and most other sites very well. They all use the same installer. As I (kinda) said before, check out i430VX's signature for a direct link to it. They will definitely work with the extended kernel; I have Serpent 52 and New Moon 28 open on my win2k system as I type. I'm not sure how it deals with limited user privileges though, as I only run as admin. I thought Iceweasel was a rebranding of Firefox for Debian. But if it's XP compatible, chances are it will work with the extended kernel. cmd.exe from XP may have a few more commands in its interpreter, but I'm not exactly sure of the differences. Yes, the last official .NET is 2.0 SP2. But BWC made ports of 3.x and 4. They take forever to install so only install those if really necessary.