Uwe Raabe

Check if fMatchResult has its Visible = True in the designer and switch it off to fix the issue.

If it is not that difficult, why don't you create such an example yourself and attach it to a bug report with all necessary steps? That would at least match the workflow Embarcadero is used to.

Is there a way to setup a shortcut to "re-run" the Delphi LSP instances?

Under Tools - Configure Tools add a new entry named Kill LSP with the following settings: Code: Program: taskkill Parameters: /IM DelphiLSP.exe /F

Fine, but there are other means to make the query fetch the complete result set. A simple Last call or setting a local index different to the query order can have the same effect.

Are you fetching the whole result set at once?

I doubt that anyone from Embarcadero can do something against a Windows internal error caused by an update. At least as long as Microsoft doesn't provide steps to work around that.

See KB5020387

Where do you get that information? To my knowledge it is Win10 21H1:

That indicates that somewhere is a direct reference to the XE5 folder in your system. Can it be that in the past you had a Professional edition with FireDAC extension and some remnants cause this?

The issue was not caused by the Delphi components itself, but by the WinApi interface they use, which acted faulty after the Windows update. As stated in my previous comment the issue is already solved with KB5020435. Thus I have no need to switch to any 3rd party component.

And you can confirm that $(BDS)\source\data\firedac is in the IDE Browsing Path and the XE5 path doesn't appear anywhere in the Delphi 11 installation nor in the project?

The $(BDS) variable is set for the current IDE when it is started. If you have multiple IDE instances open each get its own value for $(BDS). There must be something else going wrong in your installation. Is this for all projects or only for one?

Have you checked your library and browsing paths?

I can confirm that KB5020435 solves this issue on my system. As Windows Update didn't list it, I had to download and install it manually

I don't know if all is necessary, but I at least it is sufficient: have a field for the sub component exposed as a published read-property create the instance in the constructor (Self as Owner is allowed omitting the Free in the destructor) call SetSubComponent(True) after creation set all properties as needed don't forget to set Parent

There simply is no license for older Community Editions than the current one. CE licenses are restricted to one year. After that one can get a new license but for the then current version only. If you need to use an older Delphi version you are supposed to buy a full Delphi version, where the license covers older versions, too.

I guess, that is not one of the use cases the developers had in mind when they designed the custom component system. AFAIK, you can either have subcomponents created dynamically with their properties stored as sub-properties of the outer component or you can have a frame stored in the object repository with derived instances in your project.

Can you show the code for the custom component?

Yes, the problem is Windows 10 only.

I managed to get it working with the following steps: In the registry add a subkey to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols named "TLS 1.3" Add another subkey to this new key named "Client" Add a DWORD to the Client key named "Enabled" with Value = 1 Add another DWORD to the Client key named "DisabledByDefault" with Value = 0 In the TRESTClient component of your example enable TLS13 in SecureProtocols Edit: You need to restart Windows to make the registry settings active.

Currently removing the Windows Update seems the only solution.

That one is new with 11.2 and it is indeed enabled by it.

$(SanitizedProjectName) gives the name of the project without extension.

What does that garbage look like?