Request Type: BUG / NEW FEATURE MCEBuddy Version and Type (32bit or 64bit): 2.5.8 64bit - 20230215 Operating System and Type (32bit or 64bit): Windows 10 Pro 64b Summary of the problem or suggestion: With this version I keep getting the titled corruption. I’ll reset, (everything works) but er…

Thanks for reporting this. Found the issue and it’s been fixed in today’s 2.5.8 beta build. Try it out and let us know if you still have any issues. For reference the issue lay with files with a # in their names, it really wasn’t a corruption but a processing issue.

I also recently (on 2023-02-13) had my first (as far as I can remember) corrupted history file. Unfortunately, I didn’t think to capture it. I just assumed I caused it somehow. It has not yet reoccurred. (And that incident has been pruned out of mcebuddy.log.) EDIT: I’m on version 2.5.7.1. In the …

Thanks for reporting this. We just updated the INI handler in the last BETA to make it more scalable. I will be looking into this further. Can you let me know if this happens when you have a large number of files being monitors or after a specific period of time / specific number of conversions?

If you’re on an any version before 2.5.8 Feb beta version it’s not related. File corruption can happen due to fileystem issues or hardware problems. It’s very very rare but not specifically related to MCEBuddy, usually indicates an underlying disk or fileystem issue. Try running a disk repair with c…

Doesn’t really have a pattern I can discern, outside of when MCEB writes to the file. Example: After I removed the offending section from the bottom of the history file, 3 conversions started, 2 appeared to have completed, with the last one causing corruption. I’ve attached a copy of the newly cor…

Run chkdsk /f and then sfc /scannow and see if any repairs are done. I would like to know out of curiosity.

No errors, or sys. corruption and just to re-iterate, prev. build doesn’t corrupt the history file.

I encountered the same error as soon as I upgraded to the 20230215 beta build. Until 0214, there was no issue. I also take a full backup of each install before uninstall/upgrade, and tried to restore the history file from the previous install; no dice. My log file has the same errors from SharpConfi…

Thanks for the super fast turn-around @Goose , it is working now. History is visible in the app, and no errors in the log file so far. That’s a good catch, about the “#” in the filenames. Now out of curiosity, I need to check which files are these and why they have a # in their names. :slight_smile: …

Feel free to update and continue the discussion here [imagen] Update binarys General Support / Questions It might be about time to update ffmpeg and handbrake with the release of the 40 series gpus. Also, just to keep with the times, it might be nice to enable hardware enc…

I have updated handbrake in the past with no problems but if handbrake syntax were to change then that might cause problems. It seems unlikely that you would have issues but I also don’t think you should do it unless you have a good reason for it.

Corrupción del archivo de historial con MCEBuddy 2.5.8 64bit - 20230215

Errores / Solicitudes de funciones Bugs

Goose (Goose) 23 Febrero, 2023 00:13 11

Siéntete libre de actualizar y continuar la discusión aquí

Tema		Respuestas	Vistas
Unable to scan folders General Support / Questions	3	110	25 Agosto 2025
MCEBuddy has stopped converting files General Support / Questions	2	514	17 Abril 2019
MCEBuddy service not connected - corrupted history file General Support / Questions	5	2146	17 Julio 2017
History File to DB New Features	5	498	5 Abril 2023
ERROR> --> Unable to open INI file. Error : SharpConfig.ParserException: Line 7277: closing bracket missing Profiles	8	2732	22 Mayo 2018

Corrupción del archivo de historial con MCEBuddy 2.5.8 64bit - 20230215

Temas relacionados