InterLinked

OK, found it and install, looks like it worked! I didn't realize the roots update files were continually being released. I applied the roots update from 2017 and that allowed my Chromium 54 to work with HTTPS once I rebooted. I didn't need to reboot for Outlook to stop warning me, though. Interesting. Complete guide should now be fully up to date: https://w2k.phreaknet.org/guide/ I don't think anything has been left out. Just out of curiosity, when you go to Tools -> Account Settings, what do you see? I don't see my mail account listed there. I haven't, this whole time we've been testing. I thought it was something weird, but I think it's more like the Office activation think where I had to replaced riched20 dll for that to work right. You can see that something is highlighted, but there's no text. If you click Change, then the email account settings come up. Not a big issue, since there's no need to access this on a day to day basis, but I can imagine it might be confusing once I put 10 accounts in here and they all show up as invisible!

Uh, what do I click, exactly? It's all in Japanese. Usually, there's a translate option, but not this time, and there's no English really.

Did all this, when I test my settings, I get the The server you are connected to is using a security certificate that cannot be verified... A certificate chain processed correctly, but terminated in a root certificate which is not trusted by the trust provider. Do you want to continue using this server? I click Yes twice and the tests pass. Next->Finish. And then my mailbox loads!!!! Yes, it works!!! I'll have to test more of Outlook's nuances, but I will update the guide. I guess we can have our cake and eat it, too! Thanks again @win32 - really looking forward to using W2K as my primary OS now. UPDATE: In the time it took me to write this response, I went back to Outlook and it had crashed. Ah, I supposed that's to be expected, though. I do get the certificate error every time I open Outlook 2007. A very similar error happened every time I opened Outlook 2003 on vanilla W2K, but that happened twice for every single account. This happens only once, though I only have one account connected at this time. Any way to permanently disable the warning? If not, it's not the end of the world - as long as it doesn't do it once per account/server. UPDATE 2: I relaunched Outlook and tried to open an email, and then it crashed again. But I did it again and it didn't crash, so I guess it's not consistent.

Wow, I'm an id***. I looked in Program Files\Office12, not Common Files\Microsoft Shared\OFFICE12...

Yeah, no MSO.DLL for me. There are some DLLs and ACLs that start with MSO but not just MSO.DLL There is an MSO.ACL in the 1033 folder. Which Office do you have? I have Enterprise 2007.

Speaking of which, where IS MSO.DLL? Dependency Walker once warned me it couldn't find it (see my last screenshot). which folder is it in?

Wait, so the solution is simply replace the other 3 files we replaced with the original BWC ones? And then change MSO.DLL's ref to crypt32 to crypt33? No changes in outlook.exe, or any other DLLs necessary??

I tried patching out more references to crypt32, but there's so many of them! And if crypt32 were eliminated from outlook.exe's dependencies, is it guaranteed to work? I don't think it makes sense to change the default crypt32, because Word, PowerPoint, Excel, Publisher, etc. will all rely on those for encryption. Fixing Outlook seems more doable.

What happened? Yeah, that's what I discovered using dependency walker. Any thoughts on how we might figure this out?

But word doesn't refer to crypt32 at all, right? Also, Excel files can be encrypted too, and PPT also I think I'm a bit confused. Which DLLs need to be modified? Just outlook's credui to credui1 and then credui1's crypt32 to crypt33?

Sorry for all the dumb questions, but I've never used a hex editor. Which one do you recommend and how exactly do I do this? Won't I just see hex? Also, we know that Word clearly requires the new crypt32 as would PPT and Excel in order to open encrypted files. So a common reference can't be replaced, only Outlook's. EDIT: OK, I've just used HxD portable. There was 1 reference to crypt32 in outlook.exe I changed it to crypt33. Outlook starts, but I don't notice any changes. It's the same as before. FWIW, there are no references to crypt32 in winword.exe (and there was one in outlook.exe). This suggestions perhaps a common reference, which could get tricky. Just to be sure, I rebooted and logged into the other account (test): This time, it lets me click More Settings. When I try Test connection, I see this new dialog: The server you are connected to is using a security certificate that cannot be verified. Do you want to continue using this server? I click Yes, then I get the same password dialog again. Still doesn't work, just prompts again, so I click Cancel. Test failed: Your server does not support the connection encryption type you have specified. Try changing the encryption method... And so again, it fails. Other thoughts? Looking at the Office12 files, it's not apparent what files might contain relevant information. I tried modified a few more DLLs starting with OUTL in that directory. When I did this, I ended up back where I started: CRYPT32 not compatible! Despite changing *more* references to crypt33! Here is what I get when I used dependency walker - it seems Outlook is using both crypt32 and crypt33, and there's a file missing? Also, since I'm new to Dependency Walker, how would I check what exactly is calling the crypt32? I tried a bunch of DLLs and I've replaced them all or there are no matches. Also, when I try this with winword, through all its dependencies I don't get to crypt32. So it's not clear how winword depends on it. And, was I supposed to update a checksum manually for outlook.exe? Does it matter?

@win32 OK, so maybe I spoke too soon. Something weird has happened. Today, I opened up Outlook 2007, and I was prompted for my password. And re-prompted. Finally, I wiped the profile and started over. I can setup my account and it sends a test email successfully, but then it keeps prompting me again. This did NOT happen yesterday. I wonder if in the process of fixing encryption, I broke something in Outlook? This is very bizarre. This is with gmail, I haven't tried other servers yet. Anyways, as of now, I just either re-enter my password a million times or keep clicking Cancel, and now my mail doesn't get downloaded! But it was all working yesterday! This is unbelievable. Any thoughts? A similar thing happens in Outlook 2010 on XP when I try signing in to Microsoft Exchange. But if I connect as IMAP, it works. So I wouldn't expect MSFT Exchange to work in Outlook 2007, but this is a Gmail IMAP connection. **EDIT**: To fully test things out more, I created a NEW account (a new Windows account, called test). I just created it as a Standard/Power user. When I open the account wizard and finally click More details, all of a sudden, I get: ERROR The file CRYPT32.dll is incompatible with Microsoft Office Outlook. Install Outlook again. Zoinks! On the bright side, I just tried uninstalling Office 2007. First, it said "This program requires a newer version of Windows to run". I ran NNN4NT5, then ran it again and it successfully uninstalled. I rebooted and it's completely gone, even the service pack! So Office 2007 *can* uninstall, even in Windows 2000. Although I'd rather it come to terms with CRYPT32.dll than uninstall successfully...

I rebooted once, but then I figured if I used a fresh Replacer, I could copy over a fresh one each time and do all 3 and then reboot. So 4 reboots are not required, just 1 in theory. I've updated my guide with all the steps now: https://w2k.phreaknet.org/guide/ I think it should be complete. I will now take a closer look at Outlook 2007, now that I believe all the other issues are fixed. Encryption is fixed, Chromium HTTPS is fixed. VLC is not fixed, but with GOM I can play MKV and most MP4 files, so it's fixed I guess, though not in the way I would have liked. And Outlook 2007 is basically working so far, so everything has been going smoothly, more or less.

I used Replacer to replace the first file, and then it told be to Reboot, but after that, when I reopen the cmd to do the next one, it just says Data extraction failed. So I rebooted, and the same thing happens. It seems it only works for one file? And I'm not actually sure if it worked, even. EDIT: One needs to delete the original Replacer and copy it back again. Script can't be reused. Only one reboot is required then. And it works! I can now open my encrypted Word document! Thank you so much! I will be updating the guide with the additional instructions.

OK, I used 7Zip to extract the two exe files and I just see a bunch of ._p files. None of them has the desired name. Which ones are the right ones?

@win32When the OS is not booted??? Is there a simple way to do that, or does this involve shenanigans with Ubunutu or something? I know the Windows 7 install disc had a repair mode that gave a command prompt, but I don't know if W2K had that. I think it has a repair mode, but I don't think it gives cmd.exe access, does it? Okay, so these are the two downloads I found. One of them is not for POSReady though. I only found the XP one. Where is that one from? Security Update for WEPOS and POSReady 2009 (KB3081320) Windows XP Embedded Security Updates 11/9/2015 n/a 719 KB https://www.catalog.update.microsoft.com/Search.aspx?q=KB3081320 Security Update for Windows XP (KB2868626) Windows XP Security Updates 11/11/2013 n/a 754 KB https://www.catalog.update.microsoft.com/Search.aspx?q=KB2868626 Also, we finally found some software called the "GOM Player" that can play MP4s and MKVs. It seemed super sketchy, but I guess it's legit. It's rather ugly, and super slow to open, and sort of like VLC, but not nearly as good. But I guess it works, sort of. I couldn't get it to play one 11GB MP4 video in particular, which modern VLC plays instantly on newer Windows, but I guess perhaps that's just because of the size of the file? It played smaller MP4s and MKVs fine. AVIs worked, too. Also, apparently there are reports of recent GOM Players installing malware and adware. This was version 2.1, so I don't know when it was introduced (version 2.0 supposedly runs on Windows 9x). So that's sort of fixed, not the ideal solution, but I guess I could still use VLC for music and AVIs, even though I'd rather use WMP for music and VLC for videos.

What do you mean? I already have NNN4NT5 applied so mine thinks it's XP, too.

That just doesn't make sense to me. It says SP3 is sufficient to open these files and it used to work, I feel like. This one particular, I use all of Word's niche features, so WPS would certainly screw it up, just like Word 2003.

Seems rather random. Seemed that way with Outlook 2010, too. I'll probably know more once I used it more. I guess by random, it would always be in the middle of something. It doesn't crash when it's just idle, but rather when I'm clicking on something or trying to do something. Did the Word 2016 encrypted one open in 2000 as well? By the way, by encryption, I mean password protecting the document. I guess there are different forms of encryption in Word. Yeah, I need to use Word 2007. This Word document uses a lot of advanced Word formatting. It wouldn't even open in Word 2003, it would get all screwed up.

@win2k Good news! I picked up the nerve to finally open Outlook 2007. Surprisingly, it works! I sent a message, and purportedly that was the thing that didn't work, but I sent a message to myself and received it, and it came in my other Outlook client as well. Haven't thoroughly tested everything yet nor different mail accounts, but so far, things are looking bright. Only caveat is in ten minutes Outlook 2007 managed to crash maybe four times, but even on XP modded to Windows 2002, with Outlook 2010, that was crashing quite a bit, so I guess a bit of crashing is a small price to pay for it otherwise working.

OK, it was successful, and rebooted, but still didn't solve the encryption issue... Any other thoughts? I just opened a complex XLSX file with lots of conditional formatting and formulas, and it works fine. So with the exception of Outlook, which I haven't tried yet, most other major things seem to be working. Also, Chromium works with HTTPS now. I had to reboot just now and I guess that did something.

OK, now I get this: I'm saving the modified script, in case this actually works: Starting WSUS Offline Update (v. 9.2.5) at 22:45:55.38... Checking user's privileges... Determining system's properties... Found Microsoft Windows version: 5.0.2195.0 (w2k x86 enu sp4) Found Microsoft Office 2007 Word version: 12.0.6612.1000 (o2k7 enu sp3) Checking medium content... Medium build date: 12/06/2019 Medium does not support Microsoft Windows (w2k x86 enu). Medium supports Microsoft Office (ofc enu). Checking Windows Service Pack version... Warning: Update kbECHO is off. not found. Warning: Windows Service Pack installation file (kb) not found. Checking Windows Update Agent version... Installing most recent Windows Update Agent... Verifying integrity of ..\wsus\WindowsUpdateAgent30-x86.exe... hashdeep.exe: Audit passed Installing ..\wsus\WindowsUpdateAgent30-x86.exe... Checking Windows Installer version... 'InstallMSI' is not recognized as an internal or external command, operable program or batch file. 'InstallMSI' is not recognized as an internal or external command, operable program or batch file. Checking Windows Script Host version... 'InstallWSH' is not recognized as an internal or external command, operable program or batch file. 'InstallWSH' is not recognized as an internal or external command, operable program or batch file. Checking Internet Explorer version... 'InstallIE' is not recognized as an internal or external command, operable program or batch file. 'InstallIE' is not recognized as an internal or external command, operable program or batch file. Checking Windows Defender installation state... Checking Office Service Pack versions... Checking state of service 'Windows Update'... Verifying integrity of Windows Update catalog file... hashdeep.exe: Audit passed 22:46:34.17 - Listing ids of missing updates (please be patient, this will take a while)... 22:46:38.87 - Done. Listing ids of installed updates... Listing update files... Checking Microsoft Security Essentials installation state... Installation successful. Please reboot your system now. Ending WSUS Offline Update at 22:49:35.86... J:\wsusoffline925\wsusoffline\client\cmd>

@win32 OK, with that modification, this is the script output: Starting WSUS Offline Update (v. 9.2.5) at 22:09:59.83... Checking user's privileges... Determining system's properties... Found Microsoft Windows version: 5.0.2195.0 (w2k x86 enu sp4) Found Microsoft Office 2007 Word version: 12.0.6612.1000 (o2k7 enu sp3) Checking medium content... Medium build date: 12/06/2019 Medium does not support Microsoft Windows (w2k x86 enu). Medium supports Microsoft Office (ofc enu). Checking Windows Service Pack version... The system cannot find the batch label specified - NoSPTargetId J:\wsusoffline925\wsusoffline\client\cmd>

Just opened up New Moon and Serpent. No install, just a folder like with the Pale Moon 26.5 port for W2K. I suppose if an "installer" is needed, once could use Group Policy and run once to copy the folder from a network share into My Documents upon logon, and then create a shortcut on the desktop. Not something I need right now, but I can't think of another way to do an all user setup. I have nothing but good things to say! They work perfectly! They both play YouTube videos (as does even FF ESR 52.9). I didn't do a thorough test drive, but I went to the one site that didn't work in Pale Moon 26.5 and it works in New Moon 28! Super excited! Now I can exclusively use that! I will keep the Serpent download, but probably not use it. It looks just like the FF ESR 52.9. Actually, one thing is when Serpent is not maximized, the menu bar buttons go slightly off the top of the window. A small bug. New Moon users a different interface so there are no issues. Looks just like Pale Moon. No real reason to use Chrome anyways, so I guess I don't care about the HTTPS issues. Having Chromium is helpful though for testing local web pages. Anyways, I can check browsers off my list. Between IE6, Chromium 53, FF ESR 52.9, New Moon 28, and Serpent 52, I already have enough good browsers. I've heard of K-Meleon, but my understand is that's more of a lightweight browser, not a heavy duty, fully fledged one like these. Just curious: why do you prefer Serpent 52 to New Moon 28? Wondering if I'm missing or forgoing something here...

Really? I wasn't terribly surprised, I knew it would have SSL errors but didn't imagine it was that bad. Even real Chrome 49 on real XP has SSL issues, but not this bad, I don't think. Anyways, here's the output now: Starting WSUS Offline Update (v. 9.2.5) at 21:51:27.34... Checking user's privileges... Determining system's properties... Found Microsoft Windows version: 5.0.2195.0 (w2k x86 enu sp4) Found Microsoft Office 2007 Word version: 12.0.6612.1000 (o2k7 enu sp3) Checking medium content... Medium build date: 12/06/2019 Medium does not support Microsoft Windows (w2k x86 enu). Medium supports Microsoft Office (ofc enu). Checking Windows Service Pack version... ERROR: Environment variable OS_SP_TARGET_ID not set. Ending WSUS Offline Update at 21:51:32.17... J:\wsusoffline925\wsusoffline\client\cmd> What's weird is in cmd, it says 5.1.2600, because I ended up reapplying NNN4NT5 in order to install some software. However, this script still found 5.0.2195.0 somewhere. Just extracted them using 7-Zip, so I'll try that next. A little bit all over the place, but I guess right now I am trying to figure out: - Office encryption problems - Haven't tried Outlook yet, but will soon - Web browsers, Chromium SSL/HTTPS issues - Media players (codecs missing?) I feel like I'm forgetting something else, too, but that's already a good amount. Also, when I try running actual Chrome setup, I get "Your version of Windows is not supported", after a while. But I guess that's why Chromium4WIN2K exists!