Multiline Parser Backreferences To Previous State?

[TigerC10]

Question

Is it possible to leverage backreferences to the start_state in the continued states of a multiline parser?

Details

I'm trying to parse a WindowsUpdate.log file with the tail input. It is a tab separated value file, that looks like this:

2023-01-06	14:45:39:961	 980	2eb8	Agent	  * Found 0 updates and 94 categories in search; evaluated appl. rules of 1079 out of 1753 deployed entities
2023-01-06	14:45:39:961	 980	2eb8	Agent	Reporting status event with 17 installable, 170 installed,  0 installed pending, 0 failed and 0 downloaded updates
2023-01-06	14:45:39:961	 980	2eb8	Agent	*********
2023-01-06	14:45:39:961	 980	2eb8	Agent	**  END  **  Agent: Finding updates [CallerId = <<PROCESS>>: google_osconfig_agent.exe  Id = 765]
2023-01-06	14:45:39:961	 980	2eb8	Agent	*************
2023-01-06	14:45:39:961	7284	4334	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2023-01-06	14:45:39:961	7284	4334	COMAPI	  - Updates found = 0
2023-01-06	14:45:39:961	7284	4334	COMAPI	---------
2023-01-06	14:45:39:961	7284	4334	COMAPI	--  END  --  COMAPI: Search [ClientId = <NULL>]
2023-01-06	14:45:39:961	7284	4334	COMAPI	-------------
2023-01-06	14:55:30:403	17672	135c	Misc	===========  Logging initialized (build: 7.9.9600.19915, tz: -0800)  ===========
2023-01-06	14:55:30:403	17672	135c	Misc	  = Process: C:\Program Files\Google\OSConfig\google_osconfig_agent.exe
2023-01-06	14:55:30:403	17672	135c	Misc	  = Module: C:\Windows\System32\wuapi.dll
2023-01-06	14:55:30:403	17672	135c	COMAPI	-------------
2023-01-06	14:55:30:403	17672	135c	COMAPI	-- START --  COMAPI: Init Search [ClientId = <NULL>]
2023-01-06	14:55:30:403	17672	135c	COMAPI	---------
2023-01-06	14:55:30:403	17672	135c	COMAPI	-------------
2023-01-06	14:55:30:403	17672	135c	COMAPI	-- START --  COMAPI: Search [ClientId = <NULL>]
2023-01-06	14:55:30:403	17672	135c	COMAPI	---------

The regex looks something like this:

(?<TimeStamp>\d{4}-\d{2}-\d{2}\s\d{2}:\d{2}:\d{2}:\d{3})\s+(?<ProcessID>\d+)\s+(?<ThreadID>\w+)\s+(?<ComponentName>\w+)\s+(?<Message>.+)

Of particular note, the sentinels indicating a continued line are the values for the ProccessID, ThreadID, and ComponentName keys. When ProcessID, ThreadID and ComponentName all match with the ProcessID, ThreadID and ComponentName of the previous line, it is a continued line.

See also:
https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-logs