Results 1 to 4 of 4

Threaded View

  1. #4
    Join Date
    Nov 2015
    Location
    Christchurch, Dorset, United Kingdom
    Posts
    107

    Default Replace new broken DLLs with older working ones (last resort)

    [EDIT: This was copied from the premium ACP Expert Scheduler thread]

    I have researched the various KB's associated with the changed behaviour of the scheduler, have found eight KB.s so far, but there are probably more.

    The relevant DLL modules in Windows 10 builds 1903 through 2004 that introduced the problem scheduler growth are limited to just two:

    msjet40.dll and msrd3x40.dll

    The above reside in C:\Windows\SysWOW64 and are both JET Database components.

    These two components are a matched pair and any build versions later than: msjet40.dll v4.00.9801.20 and msrd3x40.dll v4.00.9801.19​ will cause the scheduler database growth problem.
    (mouse-right-click the files and read the current versions in the properties tab)

    Replacing later versions of these two .dll's with the last known-to-be-good versions in test VM's of builds 1903, 1909 and 2004 fixes the database growth problem without appearing to cause issues elsewhere.

    I am not a Microsoft expert and not able to test every possibly combination of Windows 10 build and application software package for compatibility issues so I can't stick my head above the parapet to say this is a cure for everyone and I don't have the programming skills necessary to create an installer that a user can run that would automatically replace these dll's with ones that work.

    However, if you are really stuck and Microsoft is slow to issue a fix you can replace the above files with the ones attached to this post and it should cure the problem until you next install a quality update.

    (Note: each Windows quality update is a cumulative roll-up and so each successive quality KBxxxxxx will bring all files up to the latest build version, even if the specific changes for the JET database are not listed in that KB's release notes, therefore after each "Patch Tuesday's" (second Tuesday of every month), quality KBxxxxxx, is installed then the two .dll's listed above will be replaced again with the problematic ones)

    Install notes:
    The existing .dll's in the SysWOW64 folder are currently owned by "Trusted Installer" and you have to change permissions for the two existing .dll's to be controlled by you, the administrator, see the webpage here if you don't know how to do this (not for Bob, he already knows this stuff):

    https://www.windowscentral.com/how-t...ers-windows-10

    After you change ownership of the two .dll's to give you control, rename the existing .dll's to OLD_msjet40.dll and OLD_msrd3x40.dll.
    Do not delete the existing .dll's, if this fix does not work you can delete the substituted versions and rename the old files back again to restore original state.

    Unzip and copy the two .dll's from the attachment into folder C:\Windows\SysWOW64.
    You should find:

    msjet40.dll version: v4.00.9801.20
    msrd3x40.dll version: v4.00.9801.19

    I have already changed permissions for the attached.dll's to "Everyone" but you may need to add permissions for your system/user if Windows 10 blocks you from copying them to the SysWOW64 folder and running them on your system.

    Reboot Windows 10, run the JET Database compression tool on your existing scheduler database and then test to see if the growth issue is resolved.

    Until Microsoft fix the problem, after each monthly quality update is installed you will have to go through the above procedure and replace the current .dll's noted above, with the older ones provided.

    To recap after a long post, you can install the latest KBxxxxxx quality updates, even update to build 2004, and then replace the two .dlls' listed above with the ones I have attached and the scheduler database growth issue should be fixed.

    As I only have access to a limited range of Windows builds and application software I can't promise that replacing the above .dll's won't cause system instability, or problems elsewhere, and I can only test up until todays date, I can't even be sure that this will work with every build of Windows 10 in use, and it is quite possible that the next quality update will not be compatible with the older .dll's provided and you will be back to square one.

    Hopefully the above may provide another option to deal with the JET Database growth issue until Microsoft come up with a permanent fix.

    William.
    Attached Files Attached Files
    Last edited by Bob Denny; Jun 19, 2020 at 19:04.

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Prevent Windows 10 Update Issues and Maybe Mitigate Bad Effects
    By Bob Denny in forum Windows 7 & 10 Operating System & Update Issues
    Replies: 0
    Last Post: Oct 7, 2019, 19:20
  2. [SOLVED] ALERT: Windows 8.1 and 10 Updates KB4056898 and KB4056892 Reported Problems
    By Bob Denny in forum Company and Product Announcements and Information
    Replies: 6
    Last Post: Jan 31, 2018, 20:45
  3. Caution: Feature update to Windows 10, version 1607
    By Colin Haig in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 1
    Last Post: Sep 23, 2016, 13:43

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •