Corrupt transaction resource manager after Windows 10 install - Super User
i have lingering problem after running clean windows 10 install (via microsoft's windows 10 media creation tool after upgrade windows 8.1 failed.
it looks transaction resource manager corrupted in way , every repair i've tried has failed. system event log full of 136 , 137 messages (every 5 seconds):
warning: default transaction resource manager on volume c: encountered error while starting , metadata reset. data contains error code. 1c00040002003000020000008800048000000000060019c000000000000000000000000000000000060019c0 error: default transaction resource manager on volume c: encountered non-retryable error , not start. data contains error code. 1c0004000200300002000000890004c000000000010100c000000000000000000000000000000000010100c0
a couple of other symptoms are:
- some windows updates failing error 0x80071a91. seems updates change system components (and therefore rely on common log file system). windows defender , malicious software tool updates install/run fine.
- the credential manager service not start error 6801: transaction support within specified resource manager not started or shutdown due error
after various searches have ...
- run
sfc /scannow
(no errors) - run
chkdsk /f
(no errors) - run
dism /online /cleanup-image /scanhealth
(no errors) - run
fsutil resource setautoreset true c:\
, rebooted - rebooted in safe mode, deleted
*.blf
*.regtran.ms
,*.tm*
files in%systemroot%\system32\smi\store\machine
,%systemroot%\config\txr
, rerunfsutil
command , rebooted - performed clean boot see if problem still remains (it does)
- run windows update troubleshooter in admin mode. says "one or more windows update components configured incorrectly" , repaired it, problem still remains
- reset windows update components based on http://support.microsoft.com/kb/971058.
none of these have fixed , i'm not sure went wrong in first place during installation. further suggestions, or third rebuild?
i tried clean boot install iso based on techbench link @hydranix noted in comments. installed correctly, still had same errors.
to fix it, had format os partition completely clean install.
Comments
Post a Comment