![thumbsplus 10 database settings thumbsplus 10 database settings](https://windows-cdn.softpedia.com/screenshots/ThumbsPlus_15.png)
THUMBSPLUS 10 DATABASE SETTINGS WINDOWS 10
Personally, If its a new computer with 1809 and you are going to share a MSAccess database on the network, I would import the registry settings and reboot the Windows 10 computer. I personally have not tested 1809 without the registry settings since it was such an issue last April for the customers that I support. The registry settings have remained intact after this upgrade. Some of our Windows 10 machines recently updated to 1809 from the 1803 version. Reply to this email directly, view it on GitHub, or mute the thread.īy default, Windows 10 will not have these registry settings applied and will have to be applied manually or through a GPO. You are receiving this because you commented. It's been just about 2 weeks with very stable operation and no database corruptions. I did not apply this to the Windows 7 64bit machines but only the to the Windows 10 64bit OS which are all running the 1803 update. The registry settings above will work as they are but they need to be applied as a group of the 3 values as listed since they all interrelate to each other regarding the Windows OS network communication settings (not the MSOffice application). All the systems that I've worked on are 64bit OS utilizing MSOffice 32bit applications. Subject: Re: Microsoft Access Database corruption ( #934)ĭWords registry keys are 32bit. You may also review the "DisableLeasing" registry settings for Windows Server 2012 or above pertaining to the server side if the fix above does not resolve your problem. "FileNotFoundCacheLifetime"=dword:00000000 Copy and save the following text to notepad and save it as "SMBCacheFix.reg" (with quotes)
THUMBSPLUS 10 DATABASE SETTINGS UPDATE
Evidently SMB changes are the culprit in the 1803 update and the following fix (and workstation reboot) worked for me which was applied to all the Windows 10 (1803) workstations in this environment. The backend database became corrupted as the Windows 10 (1803) workstations were introduced into the database and performed extensive query and table operations. For my scenario and many days and hours investigating this issue, the Windows 7 workstations had no issues accessing and sharing the network mapped backend database.