pdflatex does not work on win after todays update but does on linux

[Andreas Hirsch]

Dear Siep,

thank you for your further investigation!

Concerning the possible 'hardware error' i like to mention, that the 
same problems occour on a different machine at work.

Such an incidence seems to me not very likely possible (and your machine 
might not have a hardware problem too)

So we have three different systems with the same corrupted database?

Andreas

Siep Kroonenberg schrieb am 11.06.2021 um 11:02:
> On Fri, Jun 11, 2021 at 10:28:21AM +0200, Siep Kroonenberg wrote:
>> On Tue, Jun 08, 2021 at 01:51:49PM +0200, Andreas Hirsch wrote:
>>>
>>> Hi all,
>>>
>>> I'm using TeXLive2021, installed on my Ubuntu-Server for two OS:
>>> - x86_64-linux
>>> - win32
>>>
>>> After tonights update pdflatex for win32 does not work properly but I'm
>>> getting no error-message (see attached screenshot). It simply stops working.
>>
>> I can reproduce this with my Linux box as samba server and a KVM
>> windows 10 virtual machine, with or without mapping for the UNC path
>> to the TL installation.
>>
>> lualatex and xelatex work.
> 
> good\bye works with pdflatex.
> 
> A couple of messages in the event viewer:
> 
> svchost (1016,D,23) SRUJet: The database page read from the file
> "C:\Windows\system32\SRU\SRUDB.dat" at offset 1409024
> (0x0000000000158000) (database page 343 (0x157)) for 4096
> (0x00001000) bytes failed verification due to a persisted lost flush
> detection timestamp mismatch. The read operation will fail with
> error -1119 (0xfffffba1).  The flush state on database page 343
> (0x157) was 2 while the flush state on flush map page 0 (0x0) was 3.
> If this condition persists, restore the database from a previous
> backup. This problem is likely due to faulty hardware. Please
> contact your hardware vendor for further assistance diagnosing the
> problem.
> 
> svchost (1016,D,0) SRUJet: A bad page link (error -338) has been
> detected in a B-Tree (ObjectId: 12, PgnoRoot: 47) of database
> C:\Windows\system32\SRU\SRUDB.dat (47 => 343, 0).  Tag:
> BtMergeParentMismatchLast
> 
> Error IDs were resp. 544 and 447. Screenshot attached.
>