I don’t remember exactly what @Ezra used but yeah I can confirm repair tools are kinda the way to go if vlc fails. I recovered my hiking videos the same way. Took like 5–10 mins.
@Ezra do you remember the name of the one you used? I keep finding shady sites and don’t wanna make things worse.
Ngl easiest way I found was using repair software. Most of the free ones online are junk but I had one that actually worked on my drone footage. It rebuilds the damaged parts automatically.
@Silas true. I fixed my niece’s birthday clip using that method. but it’s tricky if you don’t have another video shot from the same camera/phone.
In that case, it’s probably the header of the mp4 that’s broken. players can’t read how the video or audio is structured. There are tools out there that rebuild headers using a “sample” healthy file from same device.
Yeah sadly I tried my friend’s mac already. no luck. Feels like the file itself is busted.
Sometimes moving it to another device works… like plug into a diff pc or try on mac? I know it sounds dumb but windows media player wouldn’t play mine while it worked on my friend’s macbook.
I tried that “convert/save” thing on vlc. it just spits out another file that also won’t play lol.
Ugh yeah I had this happen with a travel vlog once. if file size looks fine then it’s prob corruption. VLC “convert/repair” tool sometimes helps but don’t expect miracles.
I had this mp4 video i recorded last month from my cousin’s wedding. it played fine before but today when i tried opening it, it just says “can’t play this file” on both my laptop and phone. i even tried vlc, quicktime, nothing works. the file size looks normal so i don’t think it’s empty, but it just refuses to run. i honestly don’t care about anything else, i just really want this video back since it’s the only copy i have. has anyone here dealt with a broken or corrupted mp4 before? is there some way to fix this or am i screwed?
The wdfilter.sys BSOD is usually caused by faulty or outdated drivers or corrupted system files. To fix it safely, boot into Safe Mode if needed, update or roll back storage and system drivers, and run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an administrator Command Prompt. Install any pending Windows updates and scan for malware. If the issue started after installing new software, uninstall it. These steps usually fix the BSOD without affecting your files.
Error 0x80073712 happens when Windows update files are missing or corrupted. To fix it safely, first run the Windows Update Troubleshooter. Then repair system files by running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an administrator Command Prompt. If needed, reset Windows Update components using Command Prompt, then try updating again. If the problem continues, use the Windows Update Assistant to install updates manually. This process keeps your files safe.
High CPU usage by Svchost.exe (imgsvc) is usually caused by the Windows Image Acquisition (WIA) service or corrupted system files. To fix it safely, first restart the WIA service in Services. Then update Windows, scan for malware, and repair system files by running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an administrator Command Prompt. You can also disable unnecessary startup apps and restart Windows Explorer if needed. This should reduce CPU usage without affecting your files.
The “Your PIN is no longer available” error usually happens after a Windows update or corruption in the PIN settings. To fix it safely without losing files, you can remove the old PIN and set up a new one. Here’s how:
Sign in with your password instead of the PIN.
Open Settings → Accounts → Sign-in options → PIN (Windows Hello).
Click Remove to delete the corrupted PIN.
Restart your PC.
Go back to Settings → Accounts → Sign-in options → PIN, and click Add to create a new PIN.
If you can’t sign in at all, boot into Safe Mode or Windows Recovery Environment, sign in with your Microsoft account password, and follow the same steps. Your files will remain safe throughout this process.
Jace, you’re right. With RAID 5, two failed drives usually mean the array can’t rebuild on its own, but recovery can sometimes work if the failed drives are still readable or can be imaged. Software like R-Studio, UFS Explorer, ReclaiMe, or Stellar RAID Data Recovery can try a virtual rebuild without overwriting what’s left. Forcing a rebuild from the RAID controller is risky and can destroy the remaining data.
Have you checked whether the failed drives are still readable or if you can make full disk images of them before trying recovery?