Jump to content

InterLinked

Member
  • Posts

    492
  • Joined

  • Last visited

  • Days Won

    4
  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by InterLinked

  1. 2 hours ago, Vistapocalypse said:

    Hmm, @greenhillmaniac might need to take another look at his reg file then, at least the x64 version. (VistaLover and I use Vista x86 anyway.) Glad you have it working now! :)

    Yeah, I ran the one he had in there and it didn't seem to do the trick, but this one did.

    I wasn't a fan of 64-bit in the past, but the RAM limitation of 32-bit is kind of significant starting with Vista. I use 64-bit of Vista+ and 32-bit XP, W2K, and MS Office, since 64-bit Office is a joke.

  2. 9 minutes ago, Vistapocalypse said:

    Your IE9 version number depends on which cumulative security update for IE9 is installed. The last cumulative security update with a dual signature was KB4507434. (VistaLover wasn’t using that one in July 2017 because it wasn’t released until July 2019.) For those who have installed SHA-2 support, the highest possible version of IE9 remains a cutting-edge question.

    Your latest and longest post seems to be  about the reg files that were created by greenhillmaniac, who has never posted in this thread. It is possible to scrutinize the changes in a reg file without running it. I have looked at the reg files (in fact once offered some input regarding the x64 version), and recall some arguably superfluous changes that I interpreted as being for the sake of security (e.g. having SSL enabled has been unwise for years).

    If anyone running Vista x64 would like to manually edit their registry pursuant to TLS 1.1 and 1.2, see this post.

     

    That did the trick! I hadn't seen the comments regarding 64-bit vs. 32-bit, thank you it worked!

    I had examined the reg files closely myself and run various versions of it, but they were all targeting 32-bit in retrospect.

    I use Group Policy to disable insecure SSL anyways so the additional changes seem not to be necessary, just this did the trick:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"=-

  3. On 8/6/2020 at 4:04 PM, gerwin said:

    For my single user computer I did it like this:

    HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\ThemeManager

    "ThemeActive"="0"

    That disables Luna in the login screen.

    Then besides that Tweak UI has some options to configure login screen appearance.

     

    Hey, so technically this DOES disable themes but it's that awful white thing with the Luna font, not quite Windows Classic.

    So I won't be using it, but good to know that it works! Sad to know there's no way to force Windows Classic. I definitely remember it either like that or default Luna, not themes disabled entirely.

  4. @VistaLover @Vistapocalypse @win32

    OK, so something bizarre is definitely going on,

    Not sure if it had to do with the reg patches I applied.

    In Local Group Policy, I do have the option to "Use TLS 1, 1.1, 1.2 only". I toggled that on and off and it seemed to have no effect.

    However, I navigated to a site I know is TLS 1.2+ only and it worked!

    Confused, I ran a client SSL test - these were the results:

     

    This matches with Internet options - SSL 2, 3, and TLS 1 are disabled/greyed out AND I don't have any of them checked!

    How is HTTPS even working? It seems there is a huge mismatch between the settings and what's really going on... ????

    I played with the group policy settings and they do seem to do SOMETHING... when I changed it to "Use TLS 1.1 only", the aforementioned site stopped working. When I changed it back to 1, 1.1, and 1.2 only, it started working again.

    So I guess TLS 1.2 DOES work, but it's not apparent because the options don't show up in Internet Options. And SSL tests say the protocols are disabled even though it literally says TLS 1.2 for the handshake protocol!!! Any way to fix this? I've run the registry changes multiple times.

    Capture.PNG

  5. 6 hours ago, daniel_k said:

    Hi, here is my list of updates (applies to both 32-bit and 64-bit).

    Office / Project / Visio / SharePoint Designer 2010 Post-SP2:
    Definition Update for Microsoft Office 2010 (KB3115475)
    Security Update for Microsoft Access 2010 (KB4464527)
    Security Update for Microsoft Excel 2010 (KB4484415)
    Security Update for Microsoft InfoPath 2010 (KB3114414)
    Security Update for Microsoft Office 2010 (KB2553313)
    Security Update for Microsoft Office 2010 (KB2553332)
    Security Update for Microsoft Office 2010 (KB2589288)
    Security Update for Microsoft Office 2010 (KB2850016)
    Security Update for Microsoft Office 2010 (KB2880971)
    Security Update for Microsoft Office 2010 (KB2881029)
    Security Update for Microsoft Office 2010 (KB2956063)
    Security Update for Microsoft Office 2010 (KB2956076)
    Security Update for Microsoft Office 2010 (KB3114565)
    Security Update for Microsoft Office 2010 (KB3191908)
    Security Update for Microsoft Office 2010 (KB3203468)
    Security Update for Microsoft Office 2010 (KB3213626)
    Security Update for Microsoft Office 2010 (KB3213631)
    Security Update for Microsoft Office 2010 (KB3213638) - XP ONLY
    Security Update for Microsoft Office 2010 (KB4011610)
    Security Update for Microsoft Office 2010 (KB4022206)
    Security Update for Microsoft Office 2010 (KB4022208)
    Security Update for Microsoft Office 2010 (KB4484238)
    Security Update for Microsoft Office 2010 (KB4484266)
    Security Update for Microsoft OneNote 2010 (KB3114885)
    Security Update for Microsoft Outlook 2010 (KB4484382)
    Security Update for Microsoft Project 2010 (KB4484463)
    Security Update for Microsoft Publisher 2010 (KB4032216)
    Security Update for Microsoft Visio 2010 (KB4462225)
    Security Update for Microsoft Visio Viewer 2010 (KB2999465)
    Security Update for Microsoft Word 2010 (KB4461625)
    Security Update for Microsoft Word 2010 (KB4484458)
    Update for Microsoft Excel 2010 (KB2956084)
    Update for Microsoft Filter Pack 2.0 (KB3114879)
    Update for Microsoft InfoPath 2010 (KB2817369)
    Update for Microsoft Office 2010 (KB2553140)
    Update for Microsoft Office 2010 (KB2553347)
    Update for Microsoft Office 2010 (KB2553388)
    Update for Microsoft Office 2010 (KB2589298)
    Update for Microsoft Office 2010 (KB2589318)
    Update for Microsoft Office 2010 (KB2589339)
    Update for Microsoft Office 2010 (KB2589375)
    Update for Microsoft Office 2010 (KB2589386)
    Update for Microsoft Office 2010 (KB2597087)
    Update for Microsoft Office 2010 (KB2791057)
    Update for Microsoft Office 2010 (KB2825640)
    Update for Microsoft Office 2010 (KB2881030)
    Update for Microsoft Office 2010 (KB2883019)
    Update for Microsoft Office 2010 (KB3054873)
    Update for Microsoft Office 2010 (KB3054886)
    Update for Microsoft Office 2010 (KB3055047)
    Update for Microsoft Office 2010 (KB4092436)
    Update for Microsoft Office 2010 (KB4461579)
    Update for Microsoft Office 2010 (KB4461626)
    Update for Microsoft Office 2010 (KB4462172)
    Update for Microsoft Office 2010 (KB4462187)
    Update for Microsoft Office 2010 (KB4484377)
    Update for Microsoft Office 2010 (KB4484454)
    Update for Microsoft Outlook 2010 (KB3114559)
    Update for Microsoft Outlook Social Connector 2010 (KB2553308)
    Update for Microsoft PowerPoint 2010 (KB4092435)
    Update for Microsoft Project 2010 (KB3054882)
    Update for Microsoft SharePoint Designer 2010 (KB2881023)
    Update for Microsoft SharePoint Workspace 2010 (KB2760601)
    Update for Microsoft Visio 2010 (KB2881025)
    Update for Microsoft Visual Studio 2010 Tools for Office Runtime (KB3001652) - Must be run manually (.exe)

    Security Update for Microsoft Office 2010 (KB4092483) - XP-compatible MSO.DLL according to @Dave-H

    Business Contact Manager Post-SP1:
    Service Pack for Business Contact Manager for Microsoft Outlook 2010 (KB2553006)
    Security Update for Microsoft Chart Controls for Microsoft .NET Framework 3.5 Service Pack 1 (KB2500170)
    SQL Server 2008 Express SP2

    Looks like this is what I posted back in February: 

    Only difference is now some of these have been replaced with the latest KBs since then, many from July and June.

    I didn't include the Business Contact Manager updates.

  6. 7 hours ago, Vistapocalypse said:

    If you have already installed a number of Server 2008 updates, then you probably have KB4056564, which superseded KB4019276 as first noted in a June 22, 2018 post above. Otherwise, you might have downloaded a patch with incorrect bitness or for Itanium-based systems.

    I do indeed have 4056564. That doesn't explain though how come my version number is lower than yours...

    I applied the TLS reg entry and nothing has changed, either, except now all the SSL 2,3 and TLS 1 entries are grayed out!

  7. 4 minutes ago, Dave-H said:

    If you look at the Help section of Word, say, mine says 14.0.7214.5000.
    However, if I look at "Additional Version and Copyright Information", it's shown as 14.0.7254.5000.
    :dubbio:

    Hey, exactly the same for me!

    One is Office, one is Word, that's why.

    I'm thinking it's scaled back because of the DLL... that MSO.DLL must be from Oct 2018, so we'll never see it report newer than that office wide, will we?

  8. OK, so this is weird.

    I installed using what I had for February 2020 + the latest July 2020 updates and now this is weird.

    On my Windows 7, I have somewhere around November 2019 as my version.

    But my XP version is 14.0.7214

    That's October 2018, according to: https://docs.microsoft.com/en-us/officeupdates/update-history-office-2010-click-to-run

    Now that Windows Update on XP is broken, I can't even use that to see what might be missing.

    Any ideas? Unfortunately, MSFT doesn't have an official list of what updates are needed. You literally have to go through every single update since SP2 and trace dependencies. I did it once to get to November 2019 on W7, but somehow with the changes today, that's set me back to October 2018. I don't understand...

    @daniel_k any thoughts/ideas?

  9. 51 minutes ago, dencorso said:

    Yes. :yes:
    But you can edit your post here above and add a link to that topic, for easy reference, too.

    2 hours ago, daniel_k said:

    I've just finished an update list of Office 2010 (32/64-bit). The patches are automatically applied during installation.
    Anyone interested? If so, should I create a topic in the Office section?

    @daniel_k

    I've sort of done the same thing, but only for 32-bit.

    Maybe we can compare? It'd be good to know I didn't miss anything.

    I just updated my list from February to July this morning. Not a list so much as all the actual updates themselves, ready to slipstream.

    2 hours ago, Dave-H said:

    @win32?

    The user @win32

    Quote

    Anyway, glad you got it sorted out!
    I guess other MSI installs would have failed as well!
    I wonder why those files weren't registered? :)

    Yeah, something was weird! Maybe SP4, I dunno.

    Either way, I opened word and got the procedure entry point GetFinalPath... error. Time for some DLLing now!

  10. 24 minutes ago, docR said:

    Probably not the greatest security practice to man, but once I install Office I just grab the offline service pack installers and patch it locally. Call it a day. I don't use Outlook though, or rather anything that's sending/receiving information over the internet. Most documents I open (that I didn't make myself) are either converted down from Google Docs, or come from Word Online collaborations.

    Office Enterprise 2007 SP3 here.

    2007 might work a little different, I've played with it a few times but I really require 2010 so it's not something I've pursued again recently.

    SP2 slipstreamed worked fine on Vista and W7, as well with all updates slipstreamed. Even w/o them though, it's been failing on XP so XP has some other interesting issue.

  11. 6 minutes ago, Dave-H said:

    Oh right, so you can't install Office 2010 at all!
    Is there anything in the Windows Event logs which sheds any more light on what's happening?
    Office does use the Microsoft Installer, which is usually pretty good at logging what it's doing.
    You may well find further logs in your Windows TEMP folder.
    :dubbio:

    Indeed: Error: MsiInstaller

    What the heck? No idea what this could mean!

    Failed to connect to server. Error: 0x80080005

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Also in another log:

    The server {000C101C-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  12. 58 minutes ago, Dave-H said:

    What are you actually installing when you see the error?
    :dubbio:

    Microsoft Office 2010 Professional Plus, running setup.exe

    Begins but then fails a minute later, every time

    Same in Safe mode, when it fails even more quickly

    Happens even with all updates and SP2 removed, not sure what's up.

  13. 4 hours ago, Dave-H said:

    Sounds right.
    My MSO.DLL file is exactly 18,640,016 bytes, if yours matches that, it must be it!
    Drop the 86 off the file name, and check its version, it should be 14.0.7214.5000.
    :)

    @Dave-HOK, something weird is up. I try to install and I get "..encountered an error during setup."

    The same files I have used to install MSO 2010 SP2 on W7 and Vista with no issues.

  14. This is for users who have installed the unofficial SP4, but NOT the post-SP4 update pack because it does NOT work. Until there's an SP4 or the update pack is re-released without bugs, we are on our own after SP4.

    I compiled this after looking through all the purported post-SP4 update pack updates and running my own update scripts. All the update packs are missing the WannaCry update for some reason, so I threw that in obviously for the sake of completeness. So, I guess the post-SP4 update pack was incomplete to begin with - here is the list of all updates needed after SP4 (should be, but I could be missing something, too... please let me know if so)

    No reg patch needed to install POS updates. Just use a batch script to install everything and reboot. Hoping there's a good way to slipstream this but for an online update this isn't terrible...

    Post-SP4 updates list

    Part 1: Normal updates (only?)
     Installing KB3126587
     Installing KB3139398
     Installing KB3139914
     Installing KB3140709
     Installing KB3149090
     Installing KB3161949
     Installing KB3170455
     Installing KB3183431
     Installing KB3185911
     Installing KB3196718
     Installing KB3197835
     Installing KB3198510
     Installing KB4012583
     Installing KB4012584
     Installing KB4012598 (WannaCry)
     Installing KB4014652
     Installing KB4014794
     Installing KB4018466
     Installing KB4019204
     Installing KB4019276
     Installing KB4022747
     Installing KB4024323
     Installing KB4024402
     Installing KB4025218
     Installing KB4025409
     Installing KB4025497
     Installing KB4034775
     Installing KB4039384
     Installing KB4041995
     Installing KB4047211
     Installing KB4052303
     Installing KB4056564
     Installing KB4056941
     Installing KB4089082
     Installing KB4089175
     Installing KB4089453
     Installing KB4089694
     Installing KB4091756
     Installing KB4101477
     Installing KB4130957
     Installing KB4291391
     Installing KB4294413
     Installing KB4457163
     Installing KB4458000
     Installing KB4458001
     Installing KB4458006
     Installing KB4458318
     Installing KB4459091
     Installing KB4462935
     Installing KB4463103
     Installing KB4463573
     Installing KB4467689
     Installing KB4467770
     Installing KB4470118
     Installing KB4473077
     Installing KB4486463
     Installing KB4486465 (Thought to be problematic, as part of post-SP4 update pack, but seems not to be?)
     Installing KB4486468
     Installing KB4486536
     Installing KB4486538
     Installing KB4487990
     Installing KB4489493
     Installing KB4489973
     Installing KB4489977
     Installing KB4490228
     Installing KB4490501
     Installing KB4491443
     Installing KB4493341
     Installing KB4493563
     Installing KB4493790
     Installing KB4493793
     Installing KB4493794
     Installing KB4493795
     Installing KB4493796
     Installing KB4493797
     Installing KB4493927
     Installing KB4494059
     Installing KB4494528
     Installing KB4495022
     Installing KB4500331 (2019 RDP patch)
     == Press any key to restart ==

    Part 2: POS updates only
    KB2926765
    KB3126587
    KB4018556-v2
    KB4022746
    KB4025398
    KB4034044
    KB4230467
    KB4293928

    KB4338381
    KB4339284
    KB4339291
    KB4339854
    KB4340937

    KB4458003
    KB4493435-IE8

  15. Here's my final rundown, with notes:

    Seems like everything installed! I did a brief random sampling trying to hit all the bases and it seems they are all there in Add/Remove Programs +Show Updates. Beats me why nLite was incapable of making it work. It literally errored out on all of them. DISM isn't in XP so I'm not sure how else to slipstream these post-SP4 updates. Waiting for an SP5, hopefully...

    Post-SP4 updates list

    Part 1: Normal updates (only?)
     Installing KB3126587
     Installing KB3139398
     Installing KB3139914
     Installing KB3140709
     Installing KB3149090
     Installing KB3161949
     Installing KB3170455
     Installing KB3183431
     Installing KB3185911
     Installing KB3196718
     Installing KB3197835
     Installing KB3198510
     Installing KB4012583
     Installing KB4012584
     Installing KB4012598 (WannaCry)
     Installing KB4014652
     Installing KB4014794
     Installing KB4018466
     Installing KB4019204
     Installing KB4019276
     Installing KB4022747
     Installing KB4024323
     Installing KB4024402
     Installing KB4025218
     Installing KB4025409
     Installing KB4025497
     Installing KB4034775
     Installing KB4039384
     Installing KB4041995
     Installing KB4047211
     Installing KB4052303
     Installing KB4056564
     Installing KB4056941
     Installing KB4089082
     Installing KB4089175
     Installing KB4089453
     Installing KB4089694
     Installing KB4091756
     Installing KB4101477
     Installing KB4130957
     Installing KB4291391
     Installing KB4294413
     Installing KB4457163
     Installing KB4458000
     Installing KB4458001
     Installing KB4458006
     Installing KB4458318
     Installing KB4459091
     Installing KB4462935
     Installing KB4463103
     Installing KB4463573
     Installing KB4467689
     Installing KB4467770
     Installing KB4470118
     Installing KB4473077
     Installing KB4486463
     Installing KB4486465 (Thought to be problematic, as part of post-SP4 update pack, but seems not to be?)
     Installing KB4486468
     Installing KB4486536
     Installing KB4486538
     Installing KB4487990
     Installing KB4489493
     Installing KB4489973
     Installing KB4489977
     Installing KB4490228
     Installing KB4490501
     Installing KB4491443
     Installing KB4493341
     Installing KB4493563
     Installing KB4493790
     Installing KB4493793
     Installing KB4493794
     Installing KB4493795
     Installing KB4493796
     Installing KB4493797
     Installing KB4493927
     Installing KB4494059
     Installing KB4494528
     Installing KB4495022
     Installing KB4500331 (2019 RDP patch)
     == Press any key to restart ==

    Part 2: POS updates only
    KB2926765
    KB3126587
    KB4018556-v2
    KB4022746
    KB4025398
    KB4034044
    KB4230467
    KB4293928

    KB4338381
    KB4339284
    KB4339291
    KB4339854
    KB4340937

    KB4458003
    KB4493435-IE8

  16. 18 hours ago, Dylan Cruz said:

    KB2926765 KB4025218 KB4339291 KB4493435-IE8
    KB3126587 KB4025398 KB4339854 KB4493563
    KB3139398 KB4025409 KB4340937 KB4493790
    KB3139914 KB4025497 KB4457163 KB4493793
    KB3140709 KB4034044 KB4458000 KB4493794
    KB3149090 KB4034775 KB4458001 KB4493795
    KB3161949 KB4039384 KB4458003 KB4493796
    KB3170455 KB4041995 KB4458006 KB4493797
    KB3183431 KB4047211 KB4458318 KB4493927
    KB3185911 KB4052303 KB4459091 KB4494059
    KB3196718 KB4056564-v2 KB4462935 KB4494528
    KB3197835 KB4056941 KB4463103 KB4495022
    KB3198510 KB4089082 KB4463573 KB4500331
    KB4012583 KB4089175 KB4467689
    KB4012584 KB4089453-v2 KB4467770
    KB4014652 KB4089694 KB4470118
    KB4014794 KB4091756 KB4473077
    KB4018466 KB4101477 KB4486463
    KB4018556-v2 KB4130957 KB4486465
    KB4019204 KB4230467 KB4486468
    KB4019276 KB4291391 KB4486536
    KB4022746 KB4293928 KB4486538
    KB4022747 KB4294413 KB4487990
    KB4024323 KB4338381 KB4489493
    KB4024402 KB4339284 KB4489973
    KB4489977
    KB4490228
    KB4490501
    KB4491443
    KB4493341

    These are the reported post-4 updates that I didn't have and didn't install:

    KB2926765
    KB3126587
    KB4018556-v2
    KB4022746
    KB4025398
    KB4034044
    KB4230467
    KB4293928

    KB4338381
    KB4339284
    KB4339291
    KB4339854
    KB4340937

    KB4458003
    KB4493435-IE8

    Looking into these now.

    Other than that, in theory that should be everything... ? Of course, maybe harkaz is wrong and there were other updates, not sure where that list above came from exactly.

    Too bad WU is broken and I can't check for sure! I do see them all in add/remove in control panel though.

  17. 15 hours ago, Dave-H said:

    No, it's an Office file, AFAIK it's not part of Windows if Office isn't installed.
    I guess if you want to slipstream all the updates, you will need to just do that, but then replace the MSO.DLL file with version 14.0.7214.5000 after the process is finished.
    If you don't do that, you will end up with a non-functional installation.
    Must easier to do that as if you uninstall updates you will get nagged by Microsoft Update about updates being missing (if it's still working that is!)
    Just get KB4092483 from the Update Catalogue, extract the MSO.DLL from it, and replace the one installed with it.

     

    @Dave-H

    Hmm... so when I try extracting MSO.DLL from the update, I can't seem to find it. I'm using the 32 bit update here: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4092483

    There's two files - one just contains a TXT file, the other is mso-x-none. This seemed promising, but extracting it with 7-Zip just gives me an XML and an MSP, and extracting the MSP gives 198 folders all named like: #9500AF041A000014.0.7015.1000 for example. Inside, there's just a bunch of files like:

    !_Columns

    !_StringData

    !_StringPool

    !_Tables

    All are 1 KB files. Can't seem to further extract any of these. Am I doing something wrong here?

    UPDATE: I tried the EXE version from Microsoft Download and it seemed very similar.

    A bunch of TXT files and an MSO-X-NONE MSP and XML.

    Extracted the MSP, I get these same #9500... folders. There is a 8 MB PATCH_CAB file in it though, which contains, when extracted, MSO.DLL.86! It's 18 MB, I'm assuming this is it?

     

    Quote


    Whether that can be automated with a batch file or something I don't know.
    :dubbio:

    Manually extracting the MSO.DLL, probably not easily, but replacing the other one with this, not too bad. I'll do it manually but could be scripted as part of startup or installation

  18. On 3/15/2020 at 3:51 PM, ImWolf said:

    I have 2 machines currently running a version of the SP4 update. On my office machine I already had a SP3 install, so I simply double clicked the USP4-v3.1b-x86-ENU.exe file to update. On a separate machine I was doing a fresh install, so I slipstreamed this file into the installation files (of XP Pro SP3), and then used "Slipstream.bat" to update those install files again with the "PostSP4-May19" package.

    Soon, I will be replacing the MB on my office machine, so I will need to do a complete re-install of XP. I have been attempting to create the install ISO with nLite once again, but for some reason I am not able to integrate the May19 updates as I have done in the past. I have created a directory for the install files, and then used nLite to add the USP4-v3.1b service pack, and this seems to work just fine. However, after I extract the zip and use "slipstream.bat" to modify this install directory then nLite will no longer open the files for further use.

    At this point, nLite throws a dialog box at me saying "Unhandled exception has occured.....   Length cannot be less than zero.....   Parameter name:length"

    I tried using the "slipstream.bat" routine both while nLite was still active and had just updated the Service Pack, and after shutting nLite down. I have tried this on both machines (currently running XP SP4) with the same results.

    Last night I D/L again the newest package from Harkaz Google drive. The package includes a new file called "WindowsXP-SP4EOS-Rollup.exe", and extracts into a directory named "Update Rollup for Live Installations". There is no "readme" file included, so I'm not sure if this exe file should be slipstreamed into the installation files using nLite, or if it is intended to be run as a stand alone update after the setup (with USP4-v3.1b only). This latest "Rollup" is stamped Dec. 26, 2019.

    Any suggestions?

    Thanks,

    Wolf

    nLiteError.jpg

    Same thing happened to me!

    If you patch the files before creating the ISO, the ISO gets made but it freezes during install.

    When I try the single EXE after just SP4, it freezes on reboot as well.

    Seems others have had this problem, too: https://ryanvm.net/forum/viewtopic.php?p=157225#p157225

    There seems to be a reference that the "Christmas update" fixes it but I only see a May 2019 download not a December 2019 one.

    These are the updates included in the post-SP4 update pack:

    KB2926765 KB4025218 KB4339291 KB4493435-IE8
    KB3126587 KB4025398 KB4339854 KB4493563
    KB3139398 KB4025409 KB4340937 KB4493790
    KB3139914 KB4025497 KB4457163 KB4493793
    KB3140709 KB4034044 KB4458000 KB4493794
    KB3149090 KB4034775 KB4458001 KB4493795
    KB3161949 KB4039384 KB4458003 KB4493796
    KB3170455 KB4041995 KB4458006 KB4493797
    KB3183431 KB4047211 KB4458318 KB4493927
    KB3185911 KB4052303 KB4459091 KB4494059
    KB3196718 KB4056564-v2 KB4462935 KB4494528
    KB3197835 KB4056941 KB4463103 KB4495022
    KB3198510 KB4089082 KB4463573 KB4500331
    KB4012583 KB4089175 KB4467689
    KB4012584 KB4089453-v2 KB4467770
    KB4014652 KB4089694 KB4470118
    KB4014794 KB4091756 KB4473077
    KB4018466 KB4101477 KB4486463
    KB4018556-v2 KB4130957 KB4486465
    KB4019204 KB4230467 KB4486468
    KB4019276 KB4291391 KB4486536
    KB4022746 KB4293928 KB4486538
    KB4022747 KB4294413 KB4487990
    KB4024323 KB4338381 KB4489493
    KB4024402 KB4339284 KB4489973
    KB4489977
    KB4490228
    KB4490501
    KB4491443
    KB4493341

  19. 5 minutes ago, Dave-H said:

    The only thing you have to watch out for is that you don't use a version of MSO.DLL after version 14.0.7214.5000, which is the last XP compatible version.
    That was issued with KB4092483.
    All other files are fine (so far!)
    When you install KB4092483 keep a copy of its MSO.DLL file somewhere safe, and if Office programs fail to run when subsequent updates are installed, just replace MSO.DLL with the one you saved.
    Everything should then come good.
    :yes:

    Is MSO.DLL present before MSO is installed?

    Just wondering how it will work out if all the updates are slipstreamed. I can't individually pick out 4092483 from the files.

    I may be able to go in afterwards and uninstall the update from Control Panel, but I don't know if that will restore the MSO.DLL that would have existed otherwise, if that makes sense.

    Thanks for your help!

×
×
  • Create New...