Hello everyone. I was working for this company in May of this and the owner told me that instead of trying to use bootrec and other windows commands, and tools to fix corrupted boot files I could just compress and replace them freshly, but since then I've been researching how to do this but still haven't find the correct procedure. This guys was one of the most advance computer technician I've ever met. Dos anyone have an idea how to do this?
[REQUEST] How to replace corrupt boot files manually?
- Thread starter Haroon92
- Start date
Mick
Well-Known Member
- Reaction score
- 813
- Location
- Cambridge, UK
Sounds like maybe he means finding the files off a Win install ISO and manually copying them over to (usually) the system32 folder then decompressing (and therefore overwriting the damaged files). But I haven't done that in a long, long time. Similar to the way that SFC used to tell you to insert a Windows installation disk when a missing or damaged file was encountered.
ComputerRepairTech
Well-Known Member
- Reaction score
- 804
- Location
- Columbia, SC
That doesnt make sense. Thats exactly what the guy said? he said instead of using bootrec that you could fix corrupted boot files that you could just replace them? You can't just replace them the volume id has to match or whatever its called. Here is a handy website I keep bookmarked: https://neosmart.net/wiki/recovering-windows-bootloader/
Markverhyden
Well-Known Member
- Reaction score
- 11,221
- Location
- Raleigh, NC
i used to do stuff like that back in the day. When dependencies were simple, few and far between. Now it's a whole different ball game. I've tried doing that a few times with XP years ago. Never got it to work. There's a reason why we have automated tools to do this.
If one is getting the message, during a failed boot, about some missing or corrupted file it's usually because there is something more serious going on. Unless they have something extremely special and rare installed it's time for a nuke and pave, most likely with a new HD.
If one is getting the message, during a failed boot, about some missing or corrupted file it's usually because there is something more serious going on. Unless they have something extremely special and rare installed it's time for a nuke and pave, most likely with a new HD.
frase
Well-Known Member
- Reaction score
- 4,685
- Location
- Melbourne, Australia
wtf- did he also tell you to pass the left handed screwdriver?
Generally all I do is in cmd -
bootrec.exe / fixmbr
bootrec.exe /rebuildbcd
Or use Windows Essentials
If you are going to copy files over may as well N&P..hmmm very advanced tech
Generally all I do is in cmd -
bootrec.exe / fixmbr
bootrec.exe /rebuildbcd
Or use Windows Essentials
If you are going to copy files over may as well N&P..hmmm very advanced tech
Last edited:
Sky-Knight
Well-Known Member
- Reaction score
- 5,787
- Location
- Arizona
All modern OS's boot not to partition positions, but partition IDs. Because we're smart now, and we don't like systems that don't boot because you inserted a thumb drive!
Never manually muck about with a boot loader, always use the tools. Unless you want to type in 128bit GUIDs by hand... if so... knock yourself out.
Heck I don't even bother troubleshooting dead boot sectors anymore, Win10 thumb drive, push the machine over. Always works, gets every other issue, system is restored faster. If the customer doesn't have their licenses or install media, they can buy replacements. That's CHEAPER than my time dorking around with stuff like this.
Never manually muck about with a boot loader, always use the tools. Unless you want to type in 128bit GUIDs by hand... if so... knock yourself out.
Heck I don't even bother troubleshooting dead boot sectors anymore, Win10 thumb drive, push the machine over. Always works, gets every other issue, system is restored faster. If the customer doesn't have their licenses or install media, they can buy replacements. That's CHEAPER than my time dorking around with stuff like this.
Exactly so, but how is it done?
That's what he said. Thanks.
Maybe, because there was this case one time where a computer was failing to boot, and I was trying to reinstall the os but it could not, so it could truly be a HDD problem. Thanks.
Porthos
Well-Known Member
- Reaction score
- 14,299
- Location
- San Antonio Tx
If I cant fix the boot loader with my Macrium boot disk the OS gets reloaded. Simple as that. In todays Win 10 era it is not worth my time and for sure the customer will not want to pay for my time to do it the longer harder more expensive way.
I am going to ask, How long have you actually been repairing computers? Everything you are asking can be found using google and searching.
I am going to ask, How long have you actually been repairing computers? Everything you are asking can be found using google and searching.
Porthos
Well-Known Member
- Reaction score
- 14,299
- Location
- San Antonio Tx
You should be testing all drives BEFORE you do anything else. NO exceptions.
Because the automated softwares don't work.
Porthos
Well-Known Member
- Reaction score
- 14,299
- Location
- San Antonio Tx
Test the drive and if good reload the OS.
But what
if they have very important file stored on their hard drive, and not even linux can read the hard drive properly with the damaged boot files, because that was my case one time if i'm not mistaken.
not
a lot of experience, but about 3yrs now, mostly doing the business side of computer repairs. I had techs that did the tech job for me most times.
ComputerRepairTech
Well-Known Member
- Reaction score
- 804
- Location
- Columbia, SC
damaged boot files do not have an effect on the ability to pull information from the hard drive.
I could remember though not even linux could read the data either. But thinking of it it may had been that the HDD was damaged. Thanks.
Similar threads
