Instead of rebooting you can run this from an elevated command prompt:

gpupdate /force

This is useful for production servers where a restart would be inconvenient.

>The tables are located locally on the server and when when you check the files properties in Windows they are not read only. The files are not located in any System folders such "Program Files" etc.
>
>I was aware that members of the Administrators group get "standard user" rights that is why I used the Group Policy editor to disable this feature. However, after you mentioned this I went back and checked my server and realized that I had not re-booted it after making this change. Now after the reboot everything is working the way I expect.
>
>Simon
>>>Hi
>>>
>>>When I log into a new Windows 2019 Server as a member of the Administrators group and launch VFP every table I open is in readonly mode. If use "Run As Administrator" then the tables open in read/write mode. I do not understand why a member of the Administrator's group has this problem. Does anyone know how to fix this?
>>>
>>>Thanks,
>>>Simon
>>
>>Are the tables located locally on the server or on a network? Have you checked the access rights on the folder (if it resides on a network share, what are the access rights of the folder and what are the sharing rights) ?
>>Some folders (such as the C:\WINDOWS and C:\PROGRAM FILES and C:\PROGRAM FILES (x86) would be generally read-only standard users.
>>When you launch an application, generally it launches with the access rights of a "standard" user -- even if you are a member of Administrators.