Missing Manifest Files

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

The service Task Scheduler seems to work normally.
Are there any important Windows Updates available ? If so, provide a screenshot first.

Any improvements after this fix ?
 
I didn't notice any improvements.
There shouldn't be any important updates, I've kept the system up to date up until the ESU cut-off date in 2020.
I'll try to run updates next weekend.
 
Seems something went wrong on the 5th. I know it was running fine at the time but maybe after rebooting, some changes were applied that messed things up that I didn't notice at the time. Was doing startup repairs and I saw some message about a corrupt registry.
It keeps going straight into the recovery environment, which then tells me it can't fix the problem.
My other drive also isn't booting anymore -_- When I choose it as the boot device in the BIOS, it gets skipped during boot as if I hadn't chosen it at all. I can boot into it just fine when I choose a different drive with a bootloader that links to that drive but I can't boot into it directly by itself... Really strange. Never seen anything like this.
I'll have to take out all the drives to stop all this stupidity with startup repair looking at the wrong ones.
Hopefully VisualBCD will be able to do something here since the startup repairs don't seem to be able to.
 
Ok. We'll wait on your further report on the boot issue.
 
Do you have a means of repairing offline systems? If I can boot into a working system, can we run repairs on the one that isn't working?
Otherwise I'll have to restore my backup and redo the steps we've gone over here, hopefully not corrupting the registry again in the process, though with the steps we've taken I have a pretty good idea of what the initial problem likely was and may be able to get online "earlier" in the process than before, before resuming repairs.
 
Do you have a means of repairing offline systems? If I can boot into a working system, can we run repairs on the one that isn't working?
Click to expand...
Maybe but we need to know what the problem is. We can replace system files or sometimes a registry fix on a offline system.
Was doing startup repairs and I saw some message about a corrupt registry.
It keeps going straight into the recovery environment, which then tells me it can't fix the problem.
Click to expand...
Provide a screenshot or photo of those messages.
 
There is really only 1 message and it just says the registry is corrupt, and that it can't fix the problem.
If I try to boot, I get this BSOD


IMG_20241121_163848273.webpIMG_20241121_163159435.webp
 
PeterJ said:
Maybe but we need to know what the problem is. We can replace system files or sometimes a registry fix on a offline system.
Click to expand...
So at the moment I'm being told to restore the registry backup, so can we move on with a registry fix first? Otherwise I fear we may be going in circles by reverting changes we've made.
No one was able to tell me what the problem was, the only suggestion I've received at this point is to restore the registry backup.
 
So at the moment I'm being told to restore the registry backup, so can we move on with a registry fix first?
Click to expand...
Create a registry backup first, just to have a backup of the current state.
After that, restore the registry as being told to see if that solves the BSOD.
 
It solved the BSoD but now I'm back to having no internet lol
That was initially fixed with the Tweaking.com application, but I'm not sure at which point the BSoD was triggered.
I guess I'll do a system shutdown/restart between each step this time to make sure I can see the results of the changes right away, unless you want to try different steps this time?
 
That was initially fixed with the Tweaking.com application, but I'm not sure at which point the BSoD was triggered.
I guess I'll do a system shutdown/restart between each step this time to make sure I can see the results of the changes right away, unless you want to try different steps this time?
Click to expand...
Yes.
Just for clearance, the Tweaking.com fix was posted here: Missing Manifest Files
Instead of doing the 5 fixes in step 11 at ones, perform each one at a time.
When completed, reboot the machine and check if the BSOD re-appears.
 
The Tweaking.com tool prompts you to restart your PC after fixes so I probably did restarts back then too so that probably wasn't when things went wrong, otherwise I wouldn't have proceeded to the following fixes.
In any case, I've applied those fixes again without issue/problem.
Should I make a new registry backup at this point so we don't need to re-run those steps again in the future?
Should I proceed to the first fixlist sent after the Tweaking.com fixes?
 
Should I make a new registry backup at this point so we don't need to re-run those steps again in the future?
Click to expand...
Yes.

Should I proceed to the first fixlist sent after the Tweaking.com fixes?
Click to expand...
Not yet. Do that after a couple of days so we know the computer is still running fine after the Tweaking.com fixes.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top