[SOLVED] Need Help With SFC-Corrupt Files
- Thread starter Bobster52
- Start date
In the main attachment manager, along the thin section at the bottom (the actual attachments you are uploading to that post), hovering over each attachment will create a question mark and a cross symbol in the top right hand corner of that attachment icon. Clicking on the cross will allow you to delete that attachment.
You cannot delete attachments from the larger section towards the top right of the manager showing attachments from all of your posts, as this would affect posts other than the one you are currently editing.
Anyway, I would like to begin a little tidying. Can you please re-run the System Update Readiness Tool (find where you saved it to, double click on it, proceed through the usual messages, and allow it to install). Then please upload a copy of C:\Windows\Logs\CBS\CheckSUR.persist.log.
Also, do you have a copy of your Windows 7 installation disk to hand? It might help as part of the fix. If you don't, then not to worry.
However, if you do find it, when you read the writing on the top, do you see any mention of the phrases "SP1" or "Service Pack 1" on it?
Thank you,
Richard
Hello,
The situation is this: what we have tried so far hasn't worked.
Your computer has an extremely rare problem. I have seen something very similar occur before, but not exactly what is happening here. Unfortunately, the fix I can apply in the simple case cannot be applied here. Hence we have a problem.
After much searching on the internet, I can find nobody else with your exact problem. Not a single other person. I did say it was rare
What this also means is that there is no known solution for me to work off. I must research the problem myself, and find a solution myself. I have done this before with rare problems: I know how Windows Update works fairly well, and then it is just a case of thinking through the problem, trying to think what is going on internally for this state to have been reached, and what this state is. It is then a case of identifying all areas where the problem could lie, and thinking through what sort of corruption in each of these places could cause the error at hand. Or work from the other end, and think where could this corruption come from. Finally, once I have developed some theories, I must think through definitive tests to identify what is going on on your computer, but by testing on my own computer. I can then narrow down on the theories, and start from the beginning again if I have just ruled out all of my current theories. I must then apply these to the problem at hand, and design a fix for your computer. I must then, finally, think through all the possible consequences of this fix. Only now do I post to you. As I think you can see, there is a lot of work between each of my posts, hence my delay in responding sometimes.
I then get to see the results of the test. If it is successful, great. If it wasn't, then I must start at the beginning again. If the error changes, I must also start at the beginning again, but this time with two errors to think through. I have now applied this entire process three times, and with three failures (a disappointing failure, I must say. I feel extremely let down by this poor performance)
This is how I have been approaching your problem. There is no known solution. I must create one. I am pretty sure I will get there eventually, but the problem is, I am not sure I can do it quickly, within the next couple of days. I have approximately 24 hours between each post to follow the entire procedure outlines above.
I have given you an overview of how I work now.
So, what about your computer's problem specifically?
Well, basically, SFC is making a mistake. Extremely simplistically (and I must warn you, SFC is horrendously complicated when you drill down to the how it detects corruptions - ask me at your peril!), there is a folder on your computer called winsxs. This stores every possible version of the file, right from version 1, all the way up to version 10, for example.
However, only one version of the file is active at a time. This version is copied into a folder called System32 (you may have heard of it).
For you, SFC keeps swapping two versions in and out, in and out (of System32, the active copy).
So, you run it once, it copies version 2 into System32. You run it again, it copies in version 3. You run it one more time, it copies version 2 back. Repeat ad infinitum.
This is your problem. So, why is SFC continuously doing this? Well, that is what I am trying to find out. I genuinely do not know.
Well, after much research, it appears that there are multiple ways of creating this situation. *sigh*. All three fixes I have provided you are a fix for an actual way of causing this. I was not just guessing, or trying lots of stuff. I theoreticized until I came up with a theory which tested true. I reproduced this cycle on my laptop. In three different ways. And yet, the problem on your computer after fixing these persisted. This strongly suggests that there are more than three ways of causing this problem. After spending tens of hours successfully finding three causes of this problem, finding out that your computer has yet another root cause was seriously disappointing. You have such a difficult problem
I have tried absolutely everything I can at this point. I will not give up the hunt, I want to get to the bottom of this for future users with this same problem. But I cannot do this with you, as it is taking up too much of your precious time. It could take ages, it might come to nothing.
You are just going to have to trust me when I say this next part. I am not just trying to fob you off here, but it is safe to ignore this problem, and this is what I am going to suggest. The situation is that you have two files being flicked in and out. Neither are corrupt, so both will work just fine. The file in question will only be used extremely rarely, and when it is, it won't matter which version is currently active.
You might ask why I tried fixing this at all then, if it can be safely ignored. Firstly, most users don't like being told just to ignore a problem, as they are always left with a slight doubt as to whether it should have been ignored or not. I completely understand, and would feel the same. Therefore, it is best for me to find and fix the problem, and be done with it. No more worrying.
However, here, you can ignore this problem.
I am sorry it had to come to this. Are you willing to just ignore this problem? However, before I go, I would like to revert the changes made by all three fixing attempts, just to keep everything neat and tidy. Again, I am so, so sorry it came to this. I honestly gave it everything I had, tried everything, but it just wasn't enough
Richard
The situation is this: what we have tried so far hasn't worked.
Your computer has an extremely rare problem. I have seen something very similar occur before, but not exactly what is happening here. Unfortunately, the fix I can apply in the simple case cannot be applied here. Hence we have a problem.
After much searching on the internet, I can find nobody else with your exact problem. Not a single other person. I did say it was rare
What this also means is that there is no known solution for me to work off. I must research the problem myself, and find a solution myself. I have done this before with rare problems: I know how Windows Update works fairly well, and then it is just a case of thinking through the problem, trying to think what is going on internally for this state to have been reached, and what this state is. It is then a case of identifying all areas where the problem could lie, and thinking through what sort of corruption in each of these places could cause the error at hand. Or work from the other end, and think where could this corruption come from. Finally, once I have developed some theories, I must think through definitive tests to identify what is going on on your computer, but by testing on my own computer. I can then narrow down on the theories, and start from the beginning again if I have just ruled out all of my current theories. I must then apply these to the problem at hand, and design a fix for your computer. I must then, finally, think through all the possible consequences of this fix. Only now do I post to you. As I think you can see, there is a lot of work between each of my posts, hence my delay in responding sometimes.
I then get to see the results of the test. If it is successful, great. If it wasn't, then I must start at the beginning again. If the error changes, I must also start at the beginning again, but this time with two errors to think through. I have now applied this entire process three times, and with three failures (a disappointing failure, I must say. I feel extremely let down by this poor performance)
This is how I have been approaching your problem. There is no known solution. I must create one. I am pretty sure I will get there eventually, but the problem is, I am not sure I can do it quickly, within the next couple of days. I have approximately 24 hours between each post to follow the entire procedure outlines above.
I have given you an overview of how I work now.
So, what about your computer's problem specifically?
Well, basically, SFC is making a mistake. Extremely simplistically (and I must warn you, SFC is horrendously complicated when you drill down to the how it detects corruptions - ask me at your peril!), there is a folder on your computer called winsxs. This stores every possible version of the file, right from version 1, all the way up to version 10, for example.
However, only one version of the file is active at a time. This version is copied into a folder called System32 (you may have heard of it).
For you, SFC keeps swapping two versions in and out, in and out (of System32, the active copy).
So, you run it once, it copies version 2 into System32. You run it again, it copies in version 3. You run it one more time, it copies version 2 back. Repeat ad infinitum.
This is your problem. So, why is SFC continuously doing this? Well, that is what I am trying to find out. I genuinely do not know.
Well, after much research, it appears that there are multiple ways of creating this situation. *sigh*. All three fixes I have provided you are a fix for an actual way of causing this. I was not just guessing, or trying lots of stuff. I theoreticized until I came up with a theory which tested true. I reproduced this cycle on my laptop. In three different ways. And yet, the problem on your computer after fixing these persisted. This strongly suggests that there are more than three ways of causing this problem. After spending tens of hours successfully finding three causes of this problem, finding out that your computer has yet another root cause was seriously disappointing. You have such a difficult problem
I have tried absolutely everything I can at this point. I will not give up the hunt, I want to get to the bottom of this for future users with this same problem. But I cannot do this with you, as it is taking up too much of your precious time. It could take ages, it might come to nothing.
You are just going to have to trust me when I say this next part. I am not just trying to fob you off here, but it is safe to ignore this problem, and this is what I am going to suggest. The situation is that you have two files being flicked in and out. Neither are corrupt, so both will work just fine. The file in question will only be used extremely rarely, and when it is, it won't matter which version is currently active.
You might ask why I tried fixing this at all then, if it can be safely ignored. Firstly, most users don't like being told just to ignore a problem, as they are always left with a slight doubt as to whether it should have been ignored or not. I completely understand, and would feel the same. Therefore, it is best for me to find and fix the problem, and be done with it. No more worrying.
However, here, you can ignore this problem.
I am sorry it had to come to this. Are you willing to just ignore this problem? However, before I go, I would like to revert the changes made by all three fixing attempts, just to keep everything neat and tidy. Again, I am so, so sorry it came to this. I honestly gave it everything I had, tried everything, but it just wasn't enough
Richard
Good Morning Richard;
So sorry I put you through all this work, I am saddened to find that this is so hard to resolve...I appreciate the lengthly explaination as to what the problem is, and what steps you have taken to resolve it, as it helps me to better understand what is going on..
Just a bit more info on this subject, (to perhaps shed some lite, and understanding as to the underlying factors that actually created the problem) When IE9 first came out I liked the fact that it utilized the graphics GPU to help take some of the load off the CPU (having an older computer and all), however, when IE9 was first installed, and I ran a SFC, (part of my weekly maintence), It found corrupt files and fixed them. When I uninstalled IE9 and the computer converted back to IE8, SFC found no integrity violations...I installed and uninstalled numerious times encountering the same result...I then proceeded to contact Microsoft Tech Support because at that time, if one had a problem with IE9 it was free to solitice their help...The tech told me that because my copy of Vista did'nt come with SP1 that the only way to fix the problem, was to uninstall IE9, SP2, and SP1 respectively...And then do an in place repair (Upgrade)...He said he would be glad to assist me by taking control of the computer and preforming the uninstalls and then assist me with the Repair, and installing back the Service Packs..Everything went smoothly uninstalling IE9, rebooting, uninstalling SP2, rebooting, however when trying to uninstall SP1, when the computer was in the sign off screen and the message said "Configuring Updates-Do not turn off the computer"...It just seemed to hang there, for 2 hours...(much like when I uninstalled IE8, right before I notified you guys) The tech told me to let it finish, and he would call me back the next day to guide me through reinstalling the updateds...The next day, I woke up to find the computer in the same state, so after 13-14 hours I turned the computer off...After the Tech called me back, we tried to get the computer to boot, but to no avail...The tech told me there was nothing else he could do and that I would have to Wipe the hard-drive and Reinstall Vista....Great...:s6:...For the next 3 weeks I scoured forums, tried everything I could think of, and finally after using the Vista dvd was able to get back to the desk-top, however it was very unstable and continued to crash at random intervilles...Had Enough!!! Got into Bios, Booted from the DVD, had Windows format the harddrive and reinstalled Windows Vista...That was in March of 2012, it was great, like I had a "Brand-New Pute"...After Windows Update installed 312 updates, including SPP1 &SP2, I took a couple of weeks to reinstall all my programs, holding off installing IE9, SFC found no errors, everything was comming up roses, and then I installed IE9, ran a SFC, and once again It found corrupt files...I started a big "Stink" with Microsoft Tech Support, and after 8-10 contacts was told to send them a copy of the CBS Logs and they would escallate the problem to their top level tech dept., and they would formulate a "KB" Fix as a solution...That was in May and to-date no fix has been created...This August the motherboard went out on the computer and i upgraded with the same motherboard (A8N-E), but new from the Chinese Manufacturer that made them for ASUS back in 2006, using the same HDD with Vista on it...Upgraded a lot of other parts, but really like Vista, and in the long run, saved a lot of $$$.
One other bit of information, which might be useful, while refurbishing and "De-Branding" a older Hp Desktop, last month, that belonged to my Dad before he passed in 2009, for a friend of mine who needed a computer, it was very hard to totally remove his ownership from the computer...So I used the HP "Restore" feature from the Bios to wipe the drive and put a new copy of Vista 32-bit on the computer, making it like it just came out of the box new...What I noticed, while I was setting it up and it was Updating itself that Windows Update after installing SP1 & SP2, Failed to install IE8, just installed IE9 over IE7--And with only 235 Updates--I have a funny feeling that Microsoft is fully aware of this problem, as I have read in numerious forms of people with Vista & IE9 having the same problem...
Richard, I don't want you to take this the wrong way, but when you asked me if I could just ignore the problem, because it is safe and not hurting anything, I cannot justify in my own head, having something on my system causing corruption...Just wondering, how many times a system file can be corrupted before SFC can't repair it anymore, (and even if the file isn't actually corrupted) would drive me crazy...I want you to keep in mind that I do realize how hard you've been working on this problem, and how much of your time you've invested in trying to find a fix for it that works, and how much of a pest I've been, hovering over the forums, posting everyday, and waiting like a hungry dog, for a fix...But at the same time I also want you to know, that trulley from my heart, all the effort that you and you're team have put into trying to solve this problem, Is very, very, very much appreciated by me....
So, that being said, I would very much like for you to continue to look for a Fix, even if in your spare time, if you have any, and for me it does'nt matter how long it takes, its still better than having to reinstall and set up Vista again, and will just make me feel better knowing that someone is trying to find a solution...I can even force myself to only periodiclly check the forums or respond to an E-Mail....However, if that is not viable, or acceptable for you and you're team, I shall have to just consent, with a heavy heart, :s6: and let you go ahead with the process of reverting the changes made by the 3 fixes that we have already applied...
And Now; With the Holidays being right upon us, i would like to take this opportunity to wish You and you're Family, you're Team, and everyone at Sysnative, "A Most Very Merry Christmas, A Happy New Year, and All The Best That The Holiday Season Has To Offer!!!" :beerchug2:
Sincerly, Bobby Starke (Bobster52)
So sorry I put you through all this work, I am saddened to find that this is so hard to resolve...I appreciate the lengthly explaination as to what the problem is, and what steps you have taken to resolve it, as it helps me to better understand what is going on..
Just a bit more info on this subject, (to perhaps shed some lite, and understanding as to the underlying factors that actually created the problem) When IE9 first came out I liked the fact that it utilized the graphics GPU to help take some of the load off the CPU (having an older computer and all), however, when IE9 was first installed, and I ran a SFC, (part of my weekly maintence), It found corrupt files and fixed them. When I uninstalled IE9 and the computer converted back to IE8, SFC found no integrity violations...I installed and uninstalled numerious times encountering the same result...I then proceeded to contact Microsoft Tech Support because at that time, if one had a problem with IE9 it was free to solitice their help...The tech told me that because my copy of Vista did'nt come with SP1 that the only way to fix the problem, was to uninstall IE9, SP2, and SP1 respectively...And then do an in place repair (Upgrade)...He said he would be glad to assist me by taking control of the computer and preforming the uninstalls and then assist me with the Repair, and installing back the Service Packs..Everything went smoothly uninstalling IE9, rebooting, uninstalling SP2, rebooting, however when trying to uninstall SP1, when the computer was in the sign off screen and the message said "Configuring Updates-Do not turn off the computer"...It just seemed to hang there, for 2 hours...(much like when I uninstalled IE8, right before I notified you guys) The tech told me to let it finish, and he would call me back the next day to guide me through reinstalling the updateds...The next day, I woke up to find the computer in the same state, so after 13-14 hours I turned the computer off...After the Tech called me back, we tried to get the computer to boot, but to no avail...The tech told me there was nothing else he could do and that I would have to Wipe the hard-drive and Reinstall Vista....Great...:s6:...For the next 3 weeks I scoured forums, tried everything I could think of, and finally after using the Vista dvd was able to get back to the desk-top, however it was very unstable and continued to crash at random intervilles...Had Enough!!! Got into Bios, Booted from the DVD, had Windows format the harddrive and reinstalled Windows Vista...That was in March of 2012, it was great, like I had a "Brand-New Pute"...After Windows Update installed 312 updates, including SPP1 &SP2, I took a couple of weeks to reinstall all my programs, holding off installing IE9, SFC found no errors, everything was comming up roses, and then I installed IE9, ran a SFC, and once again It found corrupt files...I started a big "Stink" with Microsoft Tech Support, and after 8-10 contacts was told to send them a copy of the CBS Logs and they would escallate the problem to their top level tech dept., and they would formulate a "KB" Fix as a solution...That was in May and to-date no fix has been created...This August the motherboard went out on the computer and i upgraded with the same motherboard (A8N-E), but new from the Chinese Manufacturer that made them for ASUS back in 2006, using the same HDD with Vista on it...Upgraded a lot of other parts, but really like Vista, and in the long run, saved a lot of $$$.
One other bit of information, which might be useful, while refurbishing and "De-Branding" a older Hp Desktop, last month, that belonged to my Dad before he passed in 2009, for a friend of mine who needed a computer, it was very hard to totally remove his ownership from the computer...So I used the HP "Restore" feature from the Bios to wipe the drive and put a new copy of Vista 32-bit on the computer, making it like it just came out of the box new...What I noticed, while I was setting it up and it was Updating itself that Windows Update after installing SP1 & SP2, Failed to install IE8, just installed IE9 over IE7--And with only 235 Updates--I have a funny feeling that Microsoft is fully aware of this problem, as I have read in numerious forms of people with Vista & IE9 having the same problem...
Richard, I don't want you to take this the wrong way, but when you asked me if I could just ignore the problem, because it is safe and not hurting anything, I cannot justify in my own head, having something on my system causing corruption...Just wondering, how many times a system file can be corrupted before SFC can't repair it anymore, (and even if the file isn't actually corrupted) would drive me crazy...I want you to keep in mind that I do realize how hard you've been working on this problem, and how much of your time you've invested in trying to find a fix for it that works, and how much of a pest I've been, hovering over the forums, posting everyday, and waiting like a hungry dog, for a fix...But at the same time I also want you to know, that trulley from my heart, all the effort that you and you're team have put into trying to solve this problem, Is very, very, very much appreciated by me....
So, that being said, I would very much like for you to continue to look for a Fix, even if in your spare time, if you have any, and for me it does'nt matter how long it takes, its still better than having to reinstall and set up Vista again, and will just make me feel better knowing that someone is trying to find a solution...I can even force myself to only periodiclly check the forums or respond to an E-Mail....However, if that is not viable, or acceptable for you and you're team, I shall have to just consent, with a heavy heart, :s6: and let you go ahead with the process of reverting the changes made by the 3 fixes that we have already applied...
And Now; With the Holidays being right upon us, i would like to take this opportunity to wish You and you're Family, you're Team, and everyone at Sysnative, "A Most Very Merry Christmas, A Happy New Year, and All The Best That The Holiday Season Has To Offer!!!" :beerchug2:
Sincerly, Bobby Starke (Bobster52)
Last edited:
Hello again :)
I have taken another look, but to no avail. I truly think it is time to call it a day on this one. I have given it all that I can. The situation should not change any further from here, and no replacements are made until SFC is run. If SFC is not run, nothing changes. If you have any problems with updating in the future, I will happily take a look, but I suspect that you won't.
As a point of interest, if you ever run into the problem with those files from IE again, the fix is to uninstall IE9, then uninstall IE8, leaving you with IE7, and then install IE9 directly on top of IE7. I haven't yet seen it fail, although that isn't from a very large sample. Seems to work though :)
Thank you for the good wishes. I hope you had a great Christmas too.
However, I am going to do one last thing. I am actually going to revert this in parts. It may sound weird, but I was so sure that the final fix of the three I gave you was the answer. Oh yes, the first two were good attempts, but it felt unlikely that they could be the answer no matter the evidence before me. But the third fix...it just felt right, looked right, fitted literally perfectly with the logfiles. I was actually very surprised, and gutted, when it didn't work - it felt so...perfect. I want to revert all but the final fix, just leave it on its own and see if that does it. Perhaps the first two attempts are interfering.
Do you still have that file/folder in your Recycle Bin? If you do, can you please attempt to restore it? If you don't, I will give you a tool and an SFCFix script tomorrow to put it back.
Finally, today, please run the attached registry script, which undoes the first registry fixing attempt. But it does leave the second in place. It just feels...right.
Richard
I have taken another look, but to no avail. I truly think it is time to call it a day on this one. I have given it all that I can. The situation should not change any further from here, and no replacements are made until SFC is run. If SFC is not run, nothing changes. If you have any problems with updating in the future, I will happily take a look, but I suspect that you won't.
As a point of interest, if you ever run into the problem with those files from IE again, the fix is to uninstall IE9, then uninstall IE8, leaving you with IE7, and then install IE9 directly on top of IE7. I haven't yet seen it fail, although that isn't from a very large sample. Seems to work though :)
Thank you for the good wishes. I hope you had a great Christmas too.
However, I am going to do one last thing. I am actually going to revert this in parts. It may sound weird, but I was so sure that the final fix of the three I gave you was the answer. Oh yes, the first two were good attempts, but it felt unlikely that they could be the answer no matter the evidence before me. But the third fix...it just felt right, looked right, fitted literally perfectly with the logfiles. I was actually very surprised, and gutted, when it didn't work - it felt so...perfect. I want to revert all but the final fix, just leave it on its own and see if that does it. Perhaps the first two attempts are interfering.
Do you still have that file/folder in your Recycle Bin? If you do, can you please attempt to restore it? If you don't, I will give you a tool and an SFCFix script tomorrow to put it back.
Finally, today, please run the attached registry script, which undoes the first registry fixing attempt. But it does leave the second in place. It just feels...right.
Richard
Morning Richard;
Thanks for the reply, I ran the "Fix3.zip" file, and Then did a SFC...Seemed to do the same thing, Will include a copy in this reply, (don't know if you wanted one), But I don't know how to decipher the log...And as far as the File/Folder, (the file we deleated out of the winsxs folder on windows), that got erased through weekly maintaince, Sorry....So please send me the SFCFix and tool to put it back and instructions on how to use it...
Second thought---Does it make a difference That i ran the "Fix3.zip" before putting the deleated file back??? And lastly, if that doesnt produce any favorable results, do we revert the computer back from the fix that remains in place?, or is that not necessary???
Thanks again...Bobster52
Thanks for the reply, I ran the "Fix3.zip" file, and Then did a SFC...Seemed to do the same thing, Will include a copy in this reply, (don't know if you wanted one), But I don't know how to decipher the log...And as far as the File/Folder, (the file we deleated out of the winsxs folder on windows), that got erased through weekly maintaince, Sorry....So please send me the SFCFix and tool to put it back and instructions on how to use it...
Second thought---Does it make a difference That i ran the "Fix3.zip" before putting the deleated file back??? And lastly, if that doesnt produce any favorable results, do we revert the computer back from the fix that remains in place?, or is that not necessary???
Thanks again...Bobster52
Morning Richard;
Came up with a theory and wanted to get your opinion....Do you think removing IE9, and then installing IE8, and then IE9 (which caused this whole problem) would have any affect on SFC??? I will hold off doing anything untill I hear back from you...Thanks again....Bobster52...By The Way...Happy New Year...:dance:
Came up with a theory and wanted to get your opinion....Do you think removing IE9, and then installing IE8, and then IE9 (which caused this whole problem) would have any affect on SFC??? I will hold off doing anything untill I hear back from you...Thanks again....Bobster52...By The Way...Happy New Year...:dance:
Possibly, and I doubt it would hurt to try, but I wouldn't get your hopes up too much. The file in question has no real link to IE, and I doubt would be touched by its uninstaller. But you could try.
I know how much you want to actually fix this issue, so I have been quietly researching in my free time.
I have found one more potential cause, and it wasn't where I was looking for it. Digging through my past notes, I find a registry key I have rarely had to export before. In fact, over all these years, I have never once, not once, seen a corruption in there. Of course, there is the potential that I have missed a few corruptions in there, but I think it unlikely to be more than a very, very few for various reasons.
But, there is always a first. You have a unique issue, and now I have dusted it off, I see that there is actually quite a lot of potential your issue lies here.
Please open Elevated Command Prompt (How to start an Elevated Command Prompt in Windows 7 and Vista) and type in:
reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" %userprofile%\Desktop\RegistryExport1.reg
Then please zip up and upload RegistryExport1.reg, which will be on your Desktop.
Thank you :)
Richard
Happy New Year Richard;
Very happy you decided to give it one more look, really appreciate it!! I'm enclosing that Reg.Export file you wanted to look at, and were just wondering about a couple of things...Will that have to be added back to the registry at a later date, and also do we need to put back that other file with the SFCfix and tool??? This stuff is very intreging to me...Again....Thank you so very much, for your kind consideration concerning the problem I'm having... I'll be waiting on your reply...Bobster52
Very happy you decided to give it one more look, really appreciate it!! I'm enclosing that Reg.Export file you wanted to look at, and were just wondering about a couple of things...Will that have to be added back to the registry at a later date, and also do we need to put back that other file with the SFCfix and tool??? This stuff is very intreging to me...Again....Thank you so very much, for your kind consideration concerning the problem I'm having... I'll be waiting on your reply...Bobster52
For what it's worth, I'm having a similar (or the same) problem. In the process of diagnosing another problem, I found that 'sfc /scannnow' reports that it found, and was able to fix, corrupt files. It requests that I reboot, but when I do so and then run sfc again, it finds the same problem. From CBS.log:
I'm running 32-bit Windows Vista Enterprise SP2.
SUR does not find any problems, by the way:
I've run sfc successfully in the past. I first saw this on 2012-12-19. I have a suspicion that perhaps a December 2012 Windows Update introduced the problem.
I'm not asking for help per se, but I did want to publicly document that Bobster52 isn't the only one experiencing this issue.
Code:
2013-01-03 13:11:05, Info CSI 000001f5 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store
2013-01-03 13:11:05, Info CSI 000001f7 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store
2013-01-03 13:11:05, Info CSI 000001fb [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store
2013-01-03 13:11:05, Info CSI 000001fd [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store
2013-01-03 13:11:05, Info CSI 00000207 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store
2013-01-03 13:11:05, Info CSI 00000209 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store
2013-01-03 13:11:05, Info CSI 0000020d [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store
2013-01-03 13:11:05, Info CSI 0000020f [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from storeI'm running 32-bit Windows Vista Enterprise SP2.
SUR does not find any problems, by the way:
Code:
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 17.0
2013-01-03 11:54
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 2332
No errors detected
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.I've run sfc successfully in the past. I first saw this on 2012-12-19. I have a suspicion that perhaps a December 2012 Windows Update introduced the problem.
I'm not asking for help per se, but I did want to publicly document that Bobster52 isn't the only one experiencing this issue.
Last edited:
Hello David, and welcome to Sysnative :)
I would like to ask if it is possible to take a few logfile files from your computer? I have spent a very long time comparing Bobster52's computer to test beds and working computers, but have been unable to find a fix. I wonder if I could compare it to yours I might be able to home in on the common problem? I then might be able to create a generic fix for everyone. It would be wonderful if you could. In addition, if there is anything I can nail down, be it a solution, possible causes, anything to help the development team diagnose the issue, etc., I can report it to and discuss with Microsoft. But I need hard facts and logfile. If you are willing:
Export CBS folder
- Click the Start button
then click Computer.
- Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
- Find and double click on the Logs folder.
- Right-click on the CBS folder, and select Copy.
- Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
- Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
- A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
Please upload CBS.log to your next reply.
Next, please download the Freeware RegBak from here: Acelogix Software - Download products
Navigate to C:\Windows\RegBak\{Date}\ and copy the COMPONENTS file to your Desktop.
Now right click on it > Send to > Compressed (zipped) folder.
Then please upload it to your favourite file sharing website (it will be too big for here). If you have a Microsoft Account, SkyDrive could be a good choice: https://skydrive.live.com/
Finally, please open Elevated Command Prompt (How to start an Elevated Command Prompt in Windows 7 and Vista) and type in:
reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" %userprofile%\Desktop\RegistryExport1.reg
Then please zip up and upload RegistryExport1.reg, which will be on your Desktop.
I know this is a lot to ask, but I would appreciated it very greatly, if you are willing.
Richard
Thanks again. I am sorry about the delay between each of my posts. It takes me a long time to continue to research, and analyse such big registry exports, in my free time amongst other stuff which I need to do.
The registry "export" actually makes a copy of the data. It has not been removed from your registry, just a copy made, and a copy sent to me. If I notice anything, I can take action on it, but it doesn't need to be "put back", as no change was made.
As for the missing folder, I haven't forgotten. However, I actually want it left out for the time being. I suspect it may be tied into the issue.
A ray of hope off David's computer. Maybe, just maybe, I will have another lead to go on.
BTW, Your latest registry export showed nothing out of the ordinary. Basically, it all comes down to the first registry export. I am pretty sure that is where the problem lies, but it is really, really complex. The setup on your computer is just far, far too different to anything I am able to create to make analysis easy. It narrows my search down to about 100 possible causes. But maybe if I do a three way compare with David's computer, I stand a better chance.
Richard
Hi Richard;
Don't worry about the time between posts....I understand, and am eternally greatful that you are still working on a solution...Hope David responds back and can give you a little more insite into the problem...I will keep my fingures crossed....Thanks again....Bobster52 :thumbs_up:
Don't worry about the time between posts....I understand, and am eternally greatful that you are still working on a solution...Hope David responds back and can give you a little more insite into the problem...I will keep my fingures crossed....Thanks again....Bobster52 :thumbs_up:
Has Sysnative Forums helped you? Please consider donating to help us support the site!