Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: Tone111 on April 09, 2015, 03:52:59 am
-
Hi, for some time now I have had problems updating my Windows 7 SP1 64-bit Dell Inspiron One. I have tried numerous fixes and repairs (including the SURT and your own Windows Repair on several occasions), and nothing seems to work! :angry:
I have tried your latest (v.3.1.2) All-in-one repair which checks the windows packages and reparse points etc, and it gives me a whole loooong list of missing files, and one missing default reparse point which I tick to repair but every time I rescan it goes "missing" again!
Is there a way or procedure to add all the missing files manually or via a script? When I try Windows own Update it returns error 80073701 which I believe is a corrupt registry error, and alternative update methods (direct MS download and installation, PatchMyPC, PortUp, APUP, etc..) don't work either, although occasionally I can get the odd update to install via PortUp, despite a growing number that just won't! :cry:
Can anybody help please? If any more info is needed on anything let me know and I'll be more than happy to provide it...
Cheers, Tone
-
- Post the (long) list in your next reply. (attachment)
- Suggestions for a succesful Windows Update:
- Select "Notify before Download". Then you can do the updates when you & your system got enough time.
- When Windows asks you to restart, decline. Windows simply has to wait with updating until you shut down your system.
-
Thanks for the reply.
I have tried every setting in Windows Update that's available, and none of them work or make any difference! It won't even check for updates - I get an amber message saying I need to install an update to WU to be able to check for updates, then when I click Install Now it eventually gives me the red error message Unable to update 80073701, so that's not the issue. I can only hope that sorting out the missing service packaging files will correct the registry corruption and allow the updates to work. :confused:
Anyway, the list of missing files and reparse point error from the Pre-scan Repair is attached, please let me know what to do from here...
-
- Open "Control Panel", "Programs & features", "View installed Updates" to see how many updates were succesfully installed. On my Win 7 SP 1 system I have about 210 updates in total.
- Post that number and wait for Shane'reply.
-
Ok, well my system appears to have a different number completely! There are 323 Total updates installed (the number at the bottom of the page), and scrolling through the different categories of updates 284 are Microsoft Windows updates.
When I last ran PortUp several days ago there were about 30 more Windows updates showing as requiring installation, dating from March 15 back to 2012! Not sure what any of these numbers mean or how complete they are so am looking forward to see what Shane has to say on it...... :sleep:
-
That is a lot of missing files from the packages.
The list of files that should be in there are in the registry. So either some update didn't remove those registry keys or something removed all those files.
Windows updates looks at those files when installing an update, and if there is an error of any kind the update will simply bomb out and not install. But any update that didn't need to read any of those missing files will most likly have installed just fine.
So there are two ways to try and fix it.
1. Remove the registry keys pointing to the files, I havent tested this much yet so I dont do it.
2. Replace the missing files, which i can get for you.
If you havent done so yet try running the system readiness tool, it might help replace some of the missing files, cutting down on the number of files I need to hunt down lol
http://www.microsoft.com/en-us/download/details.aspx?id=20858
After you run and install that reboot the system then run the pre-scan again and post the log. :wink:
Shane
-
Cheers Shane. Yeah I thought it was a Long list as well! :tongue:
The PC was second hand when I bought it 3 years ago, and owned by a young lad, so I'm not sure if it's history is great. Plus I did have some malware on it last year (which is now all clean) so there's a fair chance that could have messed with the packages/registry. There are other issues - an empty Windows Features box being one, but I thought I'd start with the package files and updates first as this seems like the biggest problem, it's addressed by your repair tool :smiley: and fixing them may hopefully also solve some of the other issues!
I have tried running the SURT, several times (one of the many things I've gone through to try and put my machine right again!), and it seemed to fix things the first couple of times, but I'm not sure it is any more - I've run it again anyway as there's no harm in trying if it makes your life easier, so please find the latest Pre-scan log attached and see what you think... :undecided:
-
Oh, and a further bit of info which might be of use - I did a bit of digging through the Pre-scan log and found that ALL of the missing package files relate to only FIVE MS updates! :omg: (2633952, 2522422, 2656373, 2859903 & 2524375)
My thought was to try and uninstall the relevant KB's and then re-install them directly from the MS download, but when I went to find them on the Installed Updates list only ONE of them was there! :shocked:
I downloaded all the KB's anyway but when I tried to install the 4 'missing' ones they all said that 'This update is already installed on your computer'! :confused: So even though they're not on the list, the WUSI thinks that they Are, presumably due to some registry presence/corruption. I uninstalled the only 'present' one (2656373) and rebooted, then tried to re-install it again, and now it says that the update is not applicable to my computer! Help, hope I've not made matters any worse - I've done the Pre-scan again and checked it and it appears to be the same as the 2 I've already sent, so the package files are still missing for that one even though I've supposedly uninstalled it.... :blank:
-
This is similar to another problem I had where the presence of a un-updated version of a file prevented the updating of it (only makes sense to MS I guess), so I opened an elevated command prompt (right click on cmd.exe and Run as Administrator) then type the following lines:
net stop wuauserv
net stop BITS
cd %systemroot%/SoftwareDownload
ren Download Download.old
cd DataService
ren Dataservice.edb DataService.old
net start BITS
net start wuauserv
Then reboot TWICE, and run update.
Hopefully this will help.
-
Thanks Ruby.
I have tried this before, with little success, and also have a batch file with these commands in and several more which completely resets WU and re-registers all the dll's, and this hasn't worked either! :rolleyes: I tried your suggestion again on the off-chance and once more it's had no visible effect on the WU process ie. same errors and lack of success.
On my machine it's "SoftwareDistribution" and "DataStore.edb" though rather than the SoftwareDownload and DataService you mentioned. This may well work on some systems, but mine's apparently too corrupted/screwed up for this to have any effect, never mind. :sad:
Hopefully Shane or some other wiz will come back with something useful on the service packaging files replacement after the weekend hiatus... :artist:
-
You can try using the cmd options to remove those updates, here is how to do it
http://community.spiceworks.com/how_to/38624-uninstall-specific-windows-updates-via-cmd-or-batch-file-in-windows-7-8-and-server-2008-2012
Then once they are uninstalled you can try windows updates and see how it does. Might be a good idea to run the repair windows update sin my program after you uninstall those updates, that way windows updates starts fresh on its scan.
Shane
-
Ok Shane, so we're going to try removing the suspect updates rather than replacing the 'missing' package files, well it's certainly worth a go and presumably far easier!
Soooo, I gave it a whirl, and unfortunately it's made No difference! :sad: I ran the removal commands individually in an elevated DOS prompt, then I combined them into a batch file and ran them again with admin rights - both ways finished Very quickly (within a second or two), so I'm not sure how much they were actually doing, given that none of the 5 updates are now showing in the Installed Updates list.
Then did a power reset and booted into (normal mode) windows again. Turned the firewall off, disabled my AV, ended any non-essential running processes and ran your (newly-released!) All in One Repair again. Pre-scan turned out exactly as before with all the many package files still appearing, carried on to the repair section and ran that - a few errors appeared on the grey command box while running so that wasn't a good omen :rolleyes: then rebooted after completion and tried WU again once connected to the network. Same old error message - update required to WU which then gives 80073701 when Install Now is clicked.
So bottom line is - No change. I also tried re-running the removal commands again, this time without any switches to see what was happening, and all of them gave the same error code and message 'Element not found' - indicating that the update is not there to be removed.
I'm guessing we're going to have to remove some registry keys or such now, seeing as the suspect updates aren't installed any more and replacing any 'missing' files is going to be a waste of time? Whatever, let me know what's required and we'll take it from there, cheers.... :confused:
Tone
-
From a couple of Google links regarding that WU error code, they suggest that SP1 hasn't been properly installed and downloading it again.
http://windows.microsoft.com/en-GB/windows7/install-windows-7-service-pack-1
While you say you have SP1 does it say that when you right click on Computer or My Computer then click on Properties ?
The final solution for WU Error 80073701 is either a repair install, reinstall or a factory reset.
If it will let you reinstall SP1 and that doesn't do it, check to see what a sfc /scannow now comes up with.
If it reports that it is unable to repair some files, you can copy & paste the CBS log from Notepad to the Reply box after executing this command -
findstr /c:"[SR]" Cannot %windir%\logs\cbs\cbs.log > 0 & notepad 0
If they mean a factory reset then I think you should consider that.
-
Hi Boggin - yes it does say Service Pack 1 on computer Properties, and looking down the Installed Updates list I can see a Service Pack (KB976932) installed on 23/04/12 - I presume this is SP1!? Although as we know, the fact that it's on the list doesn't necessarily mean that it's fully or properly installed!... :rolleyes:
I have come across this SP1 info before on my travels when looking up the error message and wondered about re-installing SP1, but don't really know what's involved or whether I'd need to uninstall and reinstall all the other Windows Updates since then as well :thinking:
Also, I have considered a reset or repair install as well, but again I don't fully know what's involved or how to do it, or if it's really necessary. It would be my last resort I guess, if there's no alternative way to repair WU or Windows or SP1 while still in situ.
I'm still hoping Shane can come up with something to help - if not then I'd like to know the best way forward in a bit more detail, whether it be one of your suggestions or some other way....
Cheers
-
A repair install would be good to do, and it isnt hard, it is basically doing an upgrade to the same version.
here is how to do it :wink:
http://www.sevenforums.com/tutorials/3413-repair-install.html
You will need a Windows 7 disk that has SP1 already on it.
Shane
-
Before doing the final solution, see if SP1 will install on top of the existing SP1.
If it doesn't, then create a restore point - make sure it's there after a reboot then uninstall the KB and you may get it auto through Windows Updates or through a manual Check for updates - else use the appropriate download from my previous link.
With an OEM machine, while it could take longer to back up your personal stuff and reinstall everything afterwards, I would still prefer the factory reset.
If you don't have a Win 7 x64 SP1 disk, PM me your address and I'll burn a couple of Win 7 x64 Pro disks with the eicfg file removed and send them off to you.
With that file removed, it makes it an universal Win 7 x64 disk up to Ultimate, but you will need Dell's generic product key to activate if you want to go for the repair install, as the COA sticker key would only work if it was the same as the generic one.
Belarc Advisor will give you the product key for that as well as for any other paid for programs if you no longer have those. http://www.belarc.com/free_download.html
Also create a full external system image as well before the repair install as a safeguard.
-
Ok, well I've tried the SFC several times and it always says it's found corrupted files but was unable to fix some of them - the Findstr command you've quoted Boggin doesn't seem to do anything - is the syntax correct? It gave me the error "FINDSTR: Cannot open Cannot"! I've tried similar ones before and come up with huge lists from the CBS log which I've been unable to fathom, so I can always try this again and post it if you think it will help...
It's an OEM machine which came pre-installed so I've no installation disc :sad: I do have access to an HP laptop with Win 7 SP1 if that helps? Or I can download the (7gig!! :omg:) SP1 file from MS again if that's the route I should be going - will I need to uninstall SP1 first from the Installed Updates list or should I just try to reinstall it straight over the top (once I've spent several days downloading it! :cry:)?
I think this would be worth trying before doing the repair install, as that looks like a whole Heap of work which I don't really have time for just now, and requires the installation discs which you've kindly offered to let me have access to, if required :smiley:
Thanks for the advice, but I'm still a little unclear as to the exact steps I should be taking here, so would appreciate your help (again)
Ta...
(PS - I also don't know how to PM on this forum if we need to go down the installation discs route)
-
First of all, to PM anyone on the forum just click on their name and then on Send PM in the left pane.
That findstr command isn't my invention but from a learned source on another forum, but copy and paste the command from Option Three in http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to your command prompt and the text will list all repairs done and what it is unable to repair.
Copy & paste that into your thread and Shane may have some replacement files for you.
Without a valid retail licence key you will be unable to download anything now from MS or any other source that used to supply ISOs so as to create bootable disks.
As the "on board" sfc /scannow was unable to repair all files, with a bootable SP1 ISO disk you can perform an offboot sfc /scannow http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html
I use to have to write those steps out but have recently come across that tutorial :smiley:
A bootable Win 7 SP1 ISO disk is always handy to have even just to carry out that operation, so drop me a PM and I'll send you those disks anyway.
I'll send you two so that you'll have a spare but even though they are universal, they are only good for Win 7 64 bit versions - you require a separate one for 32 bit.
With an universal install disk when you do a repair or a clean install, I think you are prompted for which version you wish to use but that is only from what I've read and not from personal experience.
I would try and install the SP1 update on top of the existing one to see if it will take before uninstalling the KB first, but create a restore point first before each action and check to see that the restore point has been created after a reboot, because Win 7 has developed a habit in some cases of not retaining them after a reboot.
So to recap, create the restore point then try the SP1 update on top of the installed KB and if that doesn't do anything, create another restore point (although Windows will anyway) and then download the SP1 update and check to see if that has resolved the problem.
You could perform another sfc /scannow to see if it still finds files it is unable to repair.
When you get the disks just follow that tutorial to perform the offboot sfc /scannow if need be and you could use that HP machine to follow the tutorial as you work your way through it on the affected machine.
-
Okay, I hear what you're saying with all that Boggin - thanks!
A further question though, before I even get started downloading - I've gone to the instructions for installing W7 SP1 page you linked, and on there it says "1. Go to the Windows 7 Service Pack 1 download webpage on the Microsoft website, and then click Continue.
2. Choose either the 32-bit (x86) or the 64-bit (x64) version of SP1 depending on whether you're running the 32-bit or the 64-bit version of Windows 7, and then click Download."
When I click that link I don't see a "Continue" button or any option to choose 32 or 64-bit - just a big orange Download button! :confused: When I click this it gives me a list of 10 possible files which I then have to choose which to select from - do you know which of these I should be selecting? It's not immediately obvious from the names (other than the x64 references on a few...)
List as follows:
1. 7601.17514.101119-1850_Update_Sp_Wave1-GRMSP1.1_DVD.iso
2. Windows_Win7SP1.7601.17514.101119-1850.AMD64CHK.Symbols.msi
3. Windows_Win7SP1.7601.17514.101119-1850.AMD64FRE.Symbols.msi
4. Windows_Win7SP1.7601.17514.101119-1850.IA64CHK.Symbols.msi
5. Windows_Win7SP1.7601.17514.101119-1850.IA64FRE.Symbols.msi
6. Windows_Win7SP1.7601.17514.101119-1850.X86CHK.Symbols.msi
7. Windows_Win7SP1.7601.17514.101119-1850.X86FRE.Symbols.msi
8. windows6.1-KB976932-IA64.exe
9. windows6.1-KB976932-X64.exe
10. windows6.1-KB976932-X86.exe
Obviously 6, 7 & 10 are out, but which of the others do I need to select, or is it all?
Cheers.
-
I don't recognise those either but you wouldn't normally use the IA ones either.
Is this the site where you put in your product key for validation http://www.microsoft.com/en-us/software-recovery
There's a Contact Support link to the right of where you enter the product key where you should get advice on downloading the correct version.
Did you try reinstalling the SP1 update ?
-
Ha, well it was from the link that You posted me yesterday! :tongue: "From a couple of Google links regarding that WU error code, they suggest that SP1 hasn't been properly installed and downloading it again.
http://windows.microsoft.com/en-GB/windows7/install-windows-7-service-pack-1 "
Down this page there is a further link "Windows 7 Service Pack 1 download" (http://go.microsoft.com/fwlink/?LinkId=199583) which takes you to the actual download page, but doesn't give the supposed 'Continue' option or the choice of 32 or 64 bit! :confused:
I have been on the other MS site you mention for software recovery but not entered my product key to go any further - is this the place I should be downloading the SP1 from and not the one you posted? I've actually downloaded all the other files - the iso and the 6 others with 64 in the name, should I discard these? I don't know which of them to install or if they should be in any particular order - I'm slightly lost now.... :undecided:
-
Hang on, I'll just have a proper read through the SP1 article.
It was my mistake thinking that you were downloading the ISO to create a bootable disk.
-
Going by this http://www.microsoft.com/en-us/download/details.aspx?id=5842 you can use No.9 - click on Install instructions.
-
Thanks Boggin - that's the page I was on, and that answers the questions of which file/s to install from that list of 10.
So, tried to run no. 9 after shutting all running programs and no dice - went to a Preparing your system box and then said Installation was not successful and threw up error Element not found (ERROR_NOT_FOUND 0x80070490) - I guess I now need to try uninstall it from the Installed Updates list before trying to install again - is that correct?
-
Oh, and I also re-ran the SFC scan as per your link and it ran ok - your version had a stray "Cannot" in which wasn't recognized. I've attached the list of [SR] things found as it might be a bit too long for a single post...
If Shane or yourself have any ideas on anything that's in there then by all means let me know :smiley:
I've just had a look at the Installed Updates list and seen what options there are for SP1 (KB976932) and there don't appear to be any!! :confused: All the normal updates have an option to uninstall, but SP1 doesn't, so no idea where to go from here, especially as it doesn't appear in the list of Programs and Features!...
-
There was one thing that I learned in that article and that was that if SP1 came preinstalled then you won't be able to uninstall it, which is why you can't find it.
While there are a number of Google links for that error, I'm just going through the CBS log to see if this article is of any help http://beerpla.net/2011/05/06/how-to-fix-error_not_found-0x80070490-during-windows-7-sp1-installation/ but twice when I've accessed it, I got an error that IE had stopped responding - don't know if it's that web page but the forum web page was refreshed and I had to restart this post each time.
Anyway, I've identified similar lines in your CBS log to those in the article so perhaps you can follow those steps to see if SP1 will then install - but again, create a restore point before making any changes.
There's also this article which I came across by clicking an a sub link in the article. http://blogs.technet.com/b/asiasupp/archive/2011/06/20/the-error-0x80070490-element-not-found-when-you-are-installing-a-service-pack-or-update.aspx
If it doesn't install, you can decide if you want to back up your personal stuff and factory reset or for me to send you those install disks.
The offboot sfc /scannow could negate the need for either a factory reset or repair install.
-
Thanks for the info Boggin - SP1 wasn't pre-installed though - the machine was newly installed with W7 in 12/09 and SP1 was installed on the Updates list in 04/12 - so it IS on the list (Installed Updates, not Programs & Features) and I can find it, it just doesn't give an option to uninstall - does this mean that it can be installed if it came through Windows Updates or not if there's no option on the Control Panel WU page?
I'll have a read through the articles anyway and see if I can find what you're referring to and what actions I can take...
-
To uninstall a Windows Update you just usually click on it and use the Uninstall option or right clicking on it will give the same.
This article could be of some help but to determine if the SP1 back up files have been removed, run Disk Cleanup as an admin and check to see if the back up files are listed as having any MBs. http://windows.microsoft.com/en-GB/windows7/uninstall-sp1
They aren't default checked to be removed.
You would only get a prompt for SP1 through Windows Update if it was no longer installed.
-
Well that's what I thought - all the other updates (which I looked at, I haven't checked every one!) have an option to uninstall, but this option disappears when I select SP1! :confused:
Ok, ran disk cleanup as admin and found no bytes for Service Pack Backup files - I think they may have been deleted at some point when my HD got too full - is that a problem?
I'm still reading the articles you linked, not sure what to make of the entries in my CBS log really, it's been a long day.... :sleep:
-
I got your PM okay but have inadvertently replied through my gmail account's notification, so check your e-mails.
Edit - have you tried that command prompt method to see if that will uninstall it ?
-
Checked my emails and there's nothing there other than the Tweaking.com notifications. I did get one PM from you and replied to it but I don't know if you got my reply or not?
Yes, just tried the elevated command prompt method to uninstall SP1 and it gives the same error message (Element not found 80070490) as when trying to install!! :confused: so I can't install it Or uninstall it, jeez, back to the articles....
-
PM sent.
So it looks like the back up has to be there to uninstall and to reinstate, a repair install or factory reset when applicable, is required.
-
Argh, nooooo! :cry:
Well after looking at the Dell website the factory reset is Definitely the last resort as this would mean losing everything on the PC and having to re-install it all from scratch again, programs, settings, etc etc..! Not to mention a huge backup job which also hasn't been done for ages..
So I guess I'll have to wait for the disks and try the offline SFC and then repair install if that's what you recommend..?
-
Or just a thought - could I get these SP backup files from the HP laptop with W7 SP1 x64 which i have access to? If pasted them into the correct location do you think this might allow the KB to either install or uninstall?
-
I don't know if the SP1 download has a Save option where you could try downloading it onto the HP and then copying it across to run its .exe if it has one.
I think if that was possible, MS would have suggested that (or not), as that is what they suggest to run their Fixits when the affected computer is unable to connect to the Internet.
-
Ah well, it was just a thought!
Well none of the MS Fixits/troubleshooters or SURT have worked so far so if a repair install is the next option then it has to be worth a try, unless there's anything else out there that might effect a repair...
-
Shane may have some thoughts on it when he gets back on Monday - work commitments permitting, but it's a puzzle why after working okay that SP1 should be causing problems now - unless it isn't SP1.
-
Well it's actually been giving me problems for almost 18 months now, on and off - the machine first went tits up big style in Dec '13 and I've been trying to get it back to full working order ever since! I've had successes along the way and WU has worked intermittently in that time, but never for long, and installing or configuring updates always seems to be the sticking point and the thing that causes WU to stop working again, so whether SP1 is the root cause of the problems, or just a symptom of something else that's happened at some point while trying to update or remove malware or any other issue I don't know. :undecided:
I tried resolving via this forum now as I've used the All in One Repair several times over this period, and because the new version which updated recently now does the pre-scan, which throws up several things that I haven't seen previously, and thought that Shane or some other forum wiz might be able to get to the bottom of :artist:
All I know is the machine doesn't like installing anything from Microsoft, whether it be updates or Windows Live, although Office 365 went on fine earlier this year, and I can get the occasional update on via PortUp, but none using WU, and 3rd party software is usually ok...
I've perused the article you linked on fixing SP1 using the pnputil for 80070490, but my CBS log doesn't contain any references to "Failed uninstalling driver updates"; it contains plenty with the "0x80070490 – ERROR_NOT_FOUND" though, so I've pasted all these into the attached text file if this gives you anything to go on. I also couldn't find anything in the setupapi.dev.log containing "Failed to find driver update" or "FAILURE(0x00000490)" so a missing driver update doesn't seem to be the culprit as this article suggests, thanks for finding it anyway, I'm willing to try anything that might be of help until the install disks arrive... :smiley:
-
That should make it easier for Shane to make some sense of but for the most part they seem to refer to your recent attempts to install SP1.
But - when I see something like those, I tend to go into major repair mode such as a factory reset :smiley:
-
I am going to do a test in vmware on windows 7 with sp1 and see what happens.
All the files in the packages folders are listed (Or they should be) here
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
I had a user who couldnt install an update and even after replacing the corrupt files in the packages folder it wouldnt install, so I removed the registry keys for that file and the update installed.
So the test I am going to do is see what happens when I remove some keys out of there, I am also curious if you might have some things not listed in there, causing windows to think you need SP1 installed when you dont, and so when you try it errors out because it is already installed. If that is the case we can put back any missing registry keys there. But first let me see what happens when I purposely go screw up that registry location and see how windows handles it :-)
Shane
-
Ok, sounds interesting Shane - look forward to seeing how that goes then and whether anything similar can be done with mine.... :smiley:
-
Did you run Disk Cleanup as an admin to see if the SP1 back up files are still there showing as more than 0MB ?
BTW - I've seen your PM.
-
Think I answered this one at the weekend, but yes I did check and found 0Mb for the SP backup files - I seem to recall deleting them way back when I was cleaning my HD up as I read they wouldn't be required again (little did I know! :sad: )
That's when I suggested copying the backup files from the HP W7 SP1 laptop I have access to, if you know where they are on the HD, but you didn't seem to think it was possible, unless we've misunderstood each other on this? :confused:
-
From what I read, if they were missing then you wouldn't be able to uninstall SP1 but if Shane can do anything with the registry to fool Windows into thinking they aren't there, then the SP1 install could succeed.
-
Well I learned a lot on this after spending most of my day yesterday ripping apart Windows lol
There are 4 locations that have to do with the updates, C:\Windows\Winsxs, HKLM\Components (Which only loads when you check for updates and such), HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing and C:\Windows\servicing
I did all kinds of different things to see how windows updates would respond. And it comes down to this, if there is a single error in any of them the updates fail. There is no rebuild option and we are talking about 50,000+ files and 80,000+ registry keys.
I realized that the error numbers given when an update fails or the errors that are in the cbs.log file are not meant for the user, but instead meant only for the MS techs who make the updates. This is why they are always so cryptic and give no proper info on why or what is failing.
Basically if a virus went in any of those registry locations and simply removed them updates will never work again without a reinstall.
Right now my pre-scan uses the registry location to know what files to look for, but if those registry keys are gone the program wont know if any files are missing since they wont be listed. And since what keys and files are there depend on what updates are installed, there is no easy way to simply import over what we need from another system, and that is because of the insane amount of files and registry keys!
No down to a point though there is a middle ground. The system readiness tool knows how to handle all this and put things back, BUT only if it has the manifest, cat and mum files.
As you will see here you can add the files for the system readiness tool to look at and use, BUT you have to manually go and download each update of the missing files you need.
https://technet.microsoft.com/en-us/library/ee619779%28v=ws.10%29.aspx
So I am thinking of making a tool that will grab the files from a huge file repository I am making, it will download any needed files (If I have it) and then put it in the folders the system readiness tools looks at, then the user will run the ms tool and let it do the work.
I have no clue how long that will take me to make, but is worth a shot. Their tool is great for replacing missing and bad files, but it is lacking big time on the files it has. So let me see if I can make up on that slack and make it better :-)
Shane
-
@ Shane - I've sent Tony a couple of Win 7 x64 SP1 universal install disks with which he's initially going to run an offboot sfc /scannow at the weekend.
Will this be sufficient to replace any of the relevant missing/corrupt registry files ?
-
Ok, I hear what you're saying Shane - sounds pretty open ended and could possibly take quite a while...
Meanwhile I have the install disks - many thanks to our great forum member Boggin! :artist: - I could potentially run the offline SFC any time if that's worth a shot, as it doesn't take too much time, but I'm not sure how to run it though as I've never used an install disk; I won't have time to do a backup and repair install (if that's what you recommend) until the weekend or maybe even later, depending how things go and how long it takes.. :undecided:
-
The offboot sfc /scannow is pretty easy to do http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html
When you first switch the computer on, at the bottom of the screen it will prompt to press F2 for setup which is the BIOS or F12 to change the boot order, but these keys may differ with different makes of computer.
Tapping the key to change the boot order as you switch on will give you a small window where you use the cursor keys to select ODD (Optical Disk Drive) - insert the disk and press enter.
This is a one off boot order change.
After pressing any key to boot from CD/DVD as prompted, you may get a black screen with an option to press F8 rather than it taking you straight to the splash screen as in the tutorial.
Press F8 then select Safe Mode with Command Prompt which will take you to the splash screen where you can then follow the steps in the tutorial for Method One.
BTW - you got those disks pretty quick :smiley:
-
Yeah I thought so too - came first thing this morning, but unfortunately they were in 64 bits!! :wink: Ha, excuse the crap pun - no they were fine, wasn't expecting them so soon though - the marvels of our British postal service at it's (occasional) best!
Ok I'll give that a go then - I have done an offline SFC before but only from my own system repair disk, which I presume has the same files on that came from my own HD rather than the original installation files, so I'll see what difference that makes and whether it repairs anything that the 'normal' SFC can't.
Will get back as and when - may have to be from W8.1 laptop if anything goes amiss with my desktop during the operation.... :omg: fingers crossed!
-
Right, well that went, well I'm not really sure! :undecided:
I booted into the installation disk no problem and got to the recovery screen options and selected DOS prompt, as I have with my own repair disk previously. When typing the drive for the offline SFC scan I used F: (as per the instructions) which is the DVD ROM, but it said Windows Resource Protection couldn't start the service! So I tried changing it to C:, which is the RECOVERY partition - same message, and finally managed to get it to run from D:, which is the OS! :thinking:
So as expected, the scan returned the usual "found errors but was unable to fix them all", which is bound to happen as it's looking at the files on my HD isn't it, which is the same as doing a scan from within Windows itself!?
Have I done something wrong here? It seems to me that all I've done is the same thing I've done using my own system repair disk, which is pulling the info and files from the HD, so I'm not sure what we were hoping to see...
-
Using F: as in tutorial only applied to the author.
The tutorial said to check the location of the OS when it identified it.
Do it again but first enter bcdedit |find "osdevice" and use whichever partition letter that gives.
For info - that's a Pipe symbol before find and is the upper case of the backward slash.
That from your last post should confirm D which isn't necessarily what you would normally see in Windows Explorer as that tends to show Windows C:
The tutorial also said to run the offboot sfc /scannow a few times if at first it didn't come up clean, but rebooting after each.
You can also run a chkdsk from the same command prompt using the partition letter with the command chkdsk x: /r where x is the partition letter.
The offboot sfc checks for corruption against the files in the install disk as the store on the computer can be corrupt so that when the sfc /scannow is run from within Windows it is unable to replace them.
Having run either, check to see if Event Viewer has anything new to report.
-
Yeah cheers, I read further down the instructions page after I posted and already re-ran the SFC again! :tongue:
I ran DISKPART which gave F: as the DVD ROM, C: as RECOVERY, D: as OS and E: as Data Drive (which I partitioned off from my OS which is normally C: in Windows but D: offline).
I tried it using C: \ as the OFFBOOTDIR and D:\windows as the OFFWINDIR - it was still running when I left it earlier, along with a CHKDSK /R on my E:\ drive just to be sure. I'll do the same on the D: (OS) drive when I get back and the SFC's finished, then I'll reboot and recheck the SFC offline again - do those SFC drive letters look right to you now?
-
When you open Windows Explorer what does Windows have after it - C: is the normal partition for the OS and D is usually the recovery drive.
Go Start - type diskmgmt.msc and press enter - this will show which is which, but you use the same partition letter that the bcdedit |find "osdevice" gives for both sides of the sfc command.
It lists mine as C so I enter sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows.
If the bcdedit command gives yours as D then you should enter D: where mine is C:
This is my Disk Management on my older laptop and F: would be listed if I had my external HDD plugged in -
-
In Windows (Explorer) C:\ is the 'normal' (OS) drive with Windows and Users etc on, D: is the CD drive, and the small Recovery partition (only 14Gb) isn't visible, even with the show hidden/system option turned on. It shows up in diskmgmt.msc but doesn't have a letter assigned. My extra partition for Data Drive is E: (same as offline).
As mentioned earlier, when I'm offline the OS becomes D:, the RECOVERY becomes C:, the CD/DVD becomes F:, and E: remains the same.
My question is - if the offline scan is referencing files from the DVD then won't one of the switches need to include F:? Otherwise it's just referencing the system files from either the OS (D:) or the Recovery partition (C:) - when I tried using F: for both it gave the "Windows Resource Protection couldn't start the service" error! Same when I used C: (Recovery) for both - the only one that would run with both letters the same was D: (OS) :confused: The last one I left running used both C: (boot) and D: (win), but again I would expect one of these to be F: to reference the DVD repair files - once again I'm confused! :thinking: The result of that scan was the same as before BTW - unable to fix some of the corrupt files.
Oh, and the bcdedit command did nothing, just went back to the command prompt! The diskpart works fine though and gave the info above, hope all this helps...
-
When you enter the bcdedit command it should return with the partition letter on the next line then give you the next prompt to enter the next command - did you enter it correctly ?
If the files that it cannot repair are related to SP1 and your SP1 back up files have been removed which it could need to effect the repair, could be the reason for its failure and hopefully Shane can come up with an answer for that.
Fortunately now, you will be able to effect a repair install should push come to shove.
-
Hmm, strange - I just ran the bcdedit command again exactly the same as before and this time it worked and returned the OS as D:\, which confirms what diskpart has already told us. Not sure what happened there - it didn't give an error or anything, just went back to the blank command prompt, odd.... :confused: anyway it's worked now.
Okay well I'm happy to wait and see if Shane comes back with anything, or to go ahead with the repair install if he has nothing with his registry and file tweaks - at least I have a working machine which does most of the things it should, so I'll live with that and see what Shane has to say next.
Thanks again for your input and generous sending of disks - much appreciated, and I have a feeling I may be needing them soon! :thinking: but even if not I'm sure they'll be handy to have at some point.
-
Yes, it's always handy to have an install disk.
Did that sfc /scannow complete with the different partition letters ?
It beats me where Shane finds all of the time to do the in depth digging around in the system files, but I guess as he's already dug a big hole into them to produce WR, he only has to open a few new seams.
-
Yes, I've run it several times now using C:, D: and F: as the offbootdir but always D:\windows as the offwindir - every time it says it says it found corrupt files but was unable to fix some of them, so I'm not sure if it's had any effect or not as the message is always the same, however something may have been fixed in the background - is there a way to check, CBS.log or whatever?
Whatever the outcome the WU still isn't working, same old message as ever, so maybe Shane can open one of his seams and discover something that will finally fix this, else the install disks will be put to good use! :smiley:
-
I say do the repair install, it should get you back up and going and still have all your files and programs. :wink:
Shane
-
Hmm, ooookay, if that's what you recommend I'll give it a shot :rolleyes:
Any idea how long it takes, and whether there's anything I need to be aware of before I go ahead? I'm guessing maybe a full backup's advisable, just in case? If not then so much the better - I'm not the only one with data on the machine and for us both to do the huge, long overdue backups necessary will take a while, but if needs be...
I was also thinking of doing another Windows All in One Repair in safe mode before the repair install - would this be worth a try and if so which options should I select? I normally do several, but maybe I'm missing some...
-
Yes, it's always best to create a full external system image as well as backing up personal stuff separately.
Remember to back up your drivers as well from Windows\System32.
I think the repair install takes a couple of hours but Windows and MS updates from scratch can take substantially longer.
They took about 9hrs with my ~6.5meg sync speed following a factory reset.
-
Here is how to do it, shouldnt take to long, it is basically doing an upgrade to the same version
http://www.sevenforums.com/tutorials/3413-repair-install.html
Of course after words you will have a ton of windows updates to do lol
Shane
-
Oh yeah, thanks Shane - a ton of updates - can't bloody wait to install all those again! :sad: that's where my problems all started in the first place I believe.. :cry: :angry:
Anyway, did the backups, kicked the repair install off and got the compatibility issues as follows:
The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.
For these items, make the following changes:
Uninstall these programs. Open Control Panel and search for "uninstall a program".
Dell Webcam Central
Upgrading Windows will affect the following devices and/or programs:
These devices might not work properly after the upgrade. Before upgrading, we recommend updating the drivers for these devices. Cancel the upgrade, open Control Panel and search for "update device drivers", or go to the device manufacturer's website to search for updated drivers.
Modems: LGE Mobile USB Modem #2
Modems: LGE Mobile USB Modem
Sony sa0103: Sony sa0103 ADB Interface Driver
Universal Serial Bus controllers: LGE Mobile Composite USB Device
Network adapters: Belkin 54g Wireless USB Network Adapter #5
Imaging devices: Lexmark 2500 Series
Network adapters: Belkin 54g Wireless USB Network Adapter #3
Network adapters: Belkin 54g Wireless USB Network Adapter
Universal Serial Bus controllers: BlackBerry Smartphone
Ports (COM & LPT): ZTE Diagnostics Interface (COM5)
Storage controllers: VIA Card Reader Host Controller
Ports (COM & LPT): LGE Mobile USB Serial Port (COM12)
Network adapters: Belkin 54g Wireless USB Network Adapter #2
Ports (COM & LPT): ZTE NMEA Device (COM7)
Network adapters: Belkin 54g Wireless USB Network Adapter #4
Ports (COM & LPT): LGE Mobile USB Serial Port (COM10)
Ports (COM & LPT): LGE Mobile USB Serial Port (COM8)
Modems: ZTE Proprietary USB Modem
Modems: LGE Mobile USB Modem #3
These programs might not work properly after the upgrade. We recommend uninstalling these programs before upgrading. Cancel the upgrade, open Control Panel, and search for "uninstall a program". (Note: Programs marked as * can be safely reinstalled after the upgrade.)
iTunes (Please deauthorize computer prior to upgrade)
Lexmark Series Printer *
What should I do from here? Surely the Dell Webcam has been installed from the origonal build by Dell?! And what about all the other list after that - I haven't even heard of most of those things!! :confused:
-
Nothing seems to be going right with this.
See what the Win 7 Upgrade Advisor gives https://www.microsoft.com/en-gb/download/details.aspx?id=20
Without having to go back through the thread, was there a particular reason why you decided against a factory reset ?
-
Ha, yeah it seems that way! I've been living with it not being right for so long now that I just put up with it and work round it's many foibles and issues. Not ideal but not being able to effect a fix so far hasn't left me many options.
My main issue with doing a clean install/factory reset is the time aspect - I don't have lots and finding, reinstalling, reconfiguring and customising/optimising all the long list of programs on it, as well as having to reinstall all the damn Windows updates (itself quite a task which has often caused me much grief!) and my own files etc just seems like a big step too far, and one I'd rather not take if it can be avoided. Of course if there were no other option......... :thinking:
Anyway, ran the upgrade advisor (attached) and no mention of issues with Dell Webcam Central, or iTunes - the only red cross compatibility issues raised were the Lexmark printer drivers and Microsoft WSE 3.0 Runtime, which I've never even heard of, let alone use! I don't know what it's purpose is, but I can't find it on my list of programs and Features to uninstall it anyway! :confused: Is it part of Windows? I don't recall ever seeing it so I'm guessing it was either on when I got it or came as part of an update at some point, I've no idea... Everything else seems ok and compatible though! :undecided:
-
This is what I've found for that MS WSE thingy http://www.shouldiremoveit.com/Microsoft-WSE-Runtime-7281-program.aspx and http://en.wikipedia.org/wiki/Web_Services_Enhancements
It looks to have come pre-installed.
I'd leave it and Shane may comment on whether to uninstall it or not.
Have you used the link in the Advisor to update Project64 1.6 ?
Given that it's already been running okay in Win 7 (?) I'm not sure what it objects to. http://www.shouldiremoveit.com/Project64-14497-program.aspx
I'm not sure how you have come to have the wrong Lexmark drivers installed as when you installed the printer, it should have installed the correct ones.
You could go to Lexmark Support and see what they have for your model but as you would need to reinstall the printer after the repair install, that may be academic. http://support.lexmark.com/index?page=productSelection&channel=supportAndDownloads&locale=EN&userlocale=EN_UK
For the incremented USB drivers you may want to try http://www.thewindowsclub.com/usboblivion-remove-usb-traces-windows but create your own restore point first as it advises - I've never used this program but The Windows Club is normally pretty reliable, or you could use the manual method http://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7 and again, create your own restore point.
If the repair install still baulks and while it is time consuming, I would still consider the factory reset - but Shane may have a workaround to overcome Windows objections to you performing the repair install.
-
Update on that USOBlivion program.
Just given it a try out and to reinstate drivers afresh, just plug your USB devices back in and Windows loads them.
-
Ok, thanks. I've no idea on the WSE either but if it's part of Windows I'll leave it for now and see if Shane has anything to say on it.
Starting with the compatibility issues first though, and leaving the USB drivers for now, I uninstalled Procect64 as I've never used it, then Lexmark suite as I have the installation disk. After a reboot it started fine then when I tried to connect to the net it BSOD'd on me with a 3b error (SYSTEM_SERVICE_EXCEPTION) - no idea why! :undecided:
Started again and this time connected no problem, so ran Upgrade Advisor again and this time the only issue was the WSE again - funnily enough even though it's not showing up on Programs and Features panel (or CCleaner uninstall either!), it Is on the Revo Uninstaller list :omg: so potentially I could now remove it if it's still proving a hindrance to the repair install, which I'm now going to try again.... (apparently it's part of the .NET framework installation so whether it can be uninstalled safely without affecting that I don't know)
So, second try, pretty much the same as last time -
The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.
For these items, make the following changes:
Uninstall these programs. Open Control Panel and search for "uninstall a program".
Dell Webcam Central
Upgrading Windows will affect the following devices and/or programs:
These devices might not work properly after the upgrade. Before upgrading, we recommend updating the drivers for these devices. Cancel the upgrade, open Control Panel and search for "update device drivers", or go to the device manufacturer's website to search for updated drivers.
Universal Serial Bus controllers: LGE Mobile Composite USB Device
Network adapters: Belkin 54g Wireless USB Network Adapter #5
Network adapters: Belkin 54g Wireless USB Network Adapter #3
Network adapters: Belkin 54g Wireless USB Network Adapter
Universal Serial Bus controllers: BlackBerry Smartphone
Ports (COM & LPT): ZTE Diagnostics Interface (COM5)
Ports (COM & LPT): LGE Mobile USB Serial Port (COM12)
Sony sa0103: Sony sa0103 ADB Interface Driver
Network adapters: Belkin 54g Wireless USB Network Adapter #2
Ports (COM & LPT): ZTE NMEA Device (COM7)
Network adapters: Belkin 54g Wireless USB Network Adapter #4
Ports (COM & LPT): LGE Mobile USB Serial Port (COM10)
Ports (COM & LPT): LGE Mobile USB Serial Port (COM8)
Modems: ZTE Proprietary USB Modem
Modems: LGE Mobile USB Modem #3
Storage controllers: VIA Card Reader Host Controller
Modems: LGE Mobile USB Modem #2
Modems: LGE Mobile USB Modem
These programs might not work properly after the upgrade. We recommend uninstalling these programs before upgrading. Cancel the upgrade, open Control Panel, and search for "uninstall a program". (Note: Programs marked as * can be safely reinstalled after the upgrade.)
iTunes (Please deauthorize computer prior to upgrade)
Updating drivers I can do if required, just not sot sure if it is! No idea why the DellWebcam should be an issue, and what does "deauthorize computer prior to upgrade" mean?? :confused: :confused:
-
It would probably be best to uninstall iTunes so that should get rid of the "deauthorize".
You seem to have quite a few for the Belkin and I'm not sure what the LGE or ZTE ones are for but you could try that USBOblivion program after creating a restore point which removes all USB drivers of those devices not installed and then plug what you need back in and Windows will reinstate them.
I don't think updating the drivers will do it for all of the Belkin ones.
I use a Logitech wireless mouse and I expected it to uninstall that but that remained intact.
I had to plug my external HDD back in for its driver to be reinstated as well as that for a Flash drive - you seem to have a lot more USB bits that you plug in.
From what I understood of the articles on WSE, it appeared to be some pre-installed but now obsolete software which is .NET Framework related.
If it's going to be a sticker to the repair install then it probably would need uninstalling, but while it would be something I would do, because I'm not 100% sure, I will leave it to Shane to advise you on that.
Can you go to Dell Support and check to see if there's a driver for the web cam so that you can reinstall it should you need to uninstall it before the repair install can go ahead. http://www.dell.com/support/home/uk/en/ukdhs1/Products/
If there is, as a try out create a restore point, uninstall the web cam and then reinstall its driver to see if the cam is reinstated.
-
Ok, iTunes is gone - didn't use it much anyway. LGE is old mobile phone software I had a few years ago, ZTE and Belkin were both on when I got it and I don't think I've ever used either! Don't know what ZTE is even, and I've tried to get Belkin to work to pick up the house wifi but it doesn't appear to work so I'm guessing the machine's not wifi enabled and was part of the wifi setup of the previous owner? I use my Sony mobile tethered for internet, plus Dell mouse & keyboard and then external HDD and that's it!
Done the USB oblivion and rechecked and it seems to have cleared all the list of stuff it originally found, so here goes with another Upgrade Advisor, then I'll try the repair install again...
-
What is the full model name of your Dell Inspiron One as they tend to have a number after the name ?
On checking for the specs, the 19 version had WiFi so it's possible the wireless card went down and the previous owner opted for an USB dongle instead of a new card.
Going into Device Manager/View/Show hidden devices/Network adapters will list what adapters are installed.
-
Yes it's an Inspiron One 19A from Mid 2009. Have copied the list of adapters to a screen shot which I've attached - it's a big list! :omg: don't know what they all mean, or why some have yellow warning triangles on, perhaps you've an idea?
|I'm just running a Dell Support Assist tool which should tell me if I need any driver updates etc..
Upgrade Advisor ran again and just listed the WSE this time as incompatible, so hopefully Shane can advise on that one...
Repair install ran and gave the same problems again - Dell Webcam and and also the previous list of all the USB drivers even though USB Oblivion has taken them all off! Do I need to reboot to reset things and run again?
-
Damn, forgot to attach the screenshot - try again! :wink:
-
It would seem there isn't a wireless card fitted but go into Device Manager/View/Show hidden devices/Network adapters, right click on each of those incremented MS Adapters - select Uninstall and confirm as you only need the original of each.
I don't know what's happened to your Teredo Tunneling Pseudo-Interface but follow these steps to repair it.
1. As an administrator from the Cmd Prompt, type then press Enter after each of these commands :-
2. netsh
3. int teredo
4. set state disabled
5. Open Device Manager/View/Show hidden devices/Network adapters right click on Teredo Tunneling Pseudo-Interface and select Uninstall
6. Open the Cmd Prompt as an administrator again and type then Enter these cmds :-
7. netsh
8. int ipv6
9. set teredo client
10. Open Device Manager/Action/Scan for new hardware.
11. Then select Show hidden devices from the View menu.
It should now display without the yellow alert.
Did you try a dummy run on uninstalling/reinstalling the web cam ?
-
Seem to be having a few problems with my machine - I haven't tried anything with the Dell Webcam yet as I was waiting for the Dell PC Assist thing to run and give me any issues. It BSOD'd on me with error 124, but then rebooted ok and ran again - webcam came up fine, but then everything ground to a halt while it was doing an extended scan so I had to power it off :sad: Windows explorer has also fallen over a few times and had to be restarted from Task Manager, so maybe the PC doesn't like the Dell Assist software :undecided:
I did manage to remove the 2 duplicate MS Isatap adapters before this happened, so now there's just one (#4), and I also followed what you said on the Teredo device but now it doesn't come up on the list at all! :omg: see attached images. I did the 'Scan for hardware changes' on devman but it's not there any more. Also, do I need to remove any of the WAN Miniports? There are 8 of these but they all have different descriptions after them so I don't know which (if any) I should remove...
-
Derr, forgot to attach the images, Again! :tongue:
-
First, the commands you have entered don't quite tally with what I'd posted which is probably why the Teredo Interface hasn't been reinstalled.
Write them down and redo.
You then need to right click on the 6to4 and the MS ISATAP adapters and select Uninstall then right click on the GBE Family Controller and select Enable - the black downward arrow next to it denotes that it has been disabled.
After you have uninstalled those adapters, click on Action then on Add legacy hardware.
When you first click on Action you may only get a Help option and if so just close it and try it again.
After clicking on Add legacy hardware click on Next - Next - Next - scroll down and select Network adapters - Next - Microsoft then on the 6to4 adapter in the right hand window - Next - and that will reinstall that one, then repeat the process and scroll down that last window to select MS ISATAP adapter - Next and that will reinstall that one.
-
Hmm, well this is what you posted - "6. Open the Cmd Prompt as an administrator again and type then Enter these cmds :-
7. netsh
8. int ipv6
9. set teredo client",
and that's exactly what I typed into the cmd prompt, twice! :rolleyes: it's what's on the image I attached, so which bit of this doesn't tally?
I've actually already enabled and updated the GBE Family Controller so that's fine now; I'll uninstall and reinstall the other 2 this eve. I also uninstalled the Dell Webcam program as well, so once I've sorted the adapters out I'll give the repair install another shot! :smiley:
-
This is what I'd typed - you haven't entered all of the commands -
1. As an administrator from the Cmd Prompt, type then press Enter after each of these commands :-
2. netsh
3. int teredo
4. set state disabled
5. Open Device Manager/View/Show hidden devices/Network adapters right click on Teredo Tunneling Pseudo-Interface and select Uninstall
6. Open the Cmd Prompt as an administrator again and type then Enter these cmds :-
7. netsh
8. int ipv6
9. set teredo client
10. Open Device Manager/Action/Scan for new hardware.
11. Then select Show hidden devices from the View menu.
It should now display without the yellow alert.
-
Ah, but I did! I entered the first 4 then closed the cmd prompt, then at 6 I opened it again!
So what's the problem with the Teredo adapter - any idea why it won't appear?
ALso I've uninstalled and reinstalled the other 2 MS ones mentioned and when reinstalling they came up with error Code 10 (won't start) and still have the yellow triangles on! :confused:
-
That Code 10 could be because of the missing Teredo Interface.
I've used those commands to reinstall mine once - I'll give them another go myself and see what happens - I'll be back.
-
Whatever is the cause - it must be contagious as when I've just gone into Device Manager, my Teredo is also showing a yellow alert and a Code 10.
Not sure if a new ISP router could have caused that ?
I'll try those commands now prior to seeing if any of my restore points will reinstate it - you could also use yours to reinstate it until we can come up with a fix, but the factory reset appears to be looming large.
-
Weird if it's affecting yours as well! Anyway, not sure whether it's academic or not as my repair install is now underway :tongue: maybe after that the adapters will be ok again, time will tell.
It's done the first bit of copying Windows files and is now gathering files, settings & programs, so fingers crossed everything goes to plan! :undecided: Removing the Dell Webcam must have allowed it to run, as that was the only red cross on the previous repair install compatibility test - the WSE issue raised by the Upgrade Advisor compatibility doesn't look to have caused any problems, so far............ :wink:
-
Well that's good news.
When I went back into Device Manager I noticed that my 6to4 and the MS ISATAP adapters had gone missing and when I tried to add the legacy hardware, I also got a Code 10 for them - but found the fix.
Below those commands in my toolbox was this link https://support.microsoft.com/en-gb/kb/929852 and scrolling down to the Fix it to Re-enable IPv6 restored the code 10 from the Teredo as well as the 6to4 and ISATAP adapters.
-
Damn, forgot to attach the screenshot - try again!
Right click on each of those with the yellow ! and uninstall them. Those are normally left over after a virus cleanup.
As for the compatibility report, you can normally ignore it, just means you will have to reinstall those after is all :-)
Shane
-
So Shane's saying I can remove the MS ISATAP and 6to4 adapters then, fair enough, but do I need the Teredo tunneling one? I tried the FixIt 50440 to re-enable IPv6 and it said it couldn't process! :teeth: Ran the the FixIt 50444 (Re-enable IPv6 on nontunnel interfaces and on IPv6 tunnel interfaces) and this processed fine, so then I rebooted and tried the 50440 again and this time it worked! Rebooted and opened the list of adapters and it wasn't there - funnily enough though the triangles have gone from the 6to4 and ISATAP so these now look ok! :confused: do I still need to remove them? Then I tried the script you sent earlier Boggin, and it ran ok but nothing happened, so I went to Add Legacy Hardware, found the Teredo Tunneling adapter and added it manually, so now it's back on the list - please let me know which of the adapters I need and don't need.
As for the repair install, welll..... when I went to bed it had been running 5 hrs or so and was on the last of 5 steps in the install process, with green ticks on the first 4, so was looking good, and I left it. This morning logged on ok and got a message that it hadn't installed this version of Windows (see attached) and mentioned compatibility issues - should I try uninstalling the WSE thing mentioned earlier, or even the whole .NET framework, and try again?
-
Well, I'm pretty certain that I removed the eicfg file from the Pro ISO on this laptop - I also have it saved on another.
Are you sure you have Win 7 x64 and not Win 7 x32
I'll run the eicfg removal utility again on this ISO and send you another couple of disks, but sorry if I've screwed up on this.
It's one of the hazards of using two laptops and age when remembering what's what.
As for the adapters, you probably don't need the 6to4 adapter, but you may need the Teredo and certainly the ISATAP adapter.
https://technet.microsoft.com/en-us/network/cc917486.aspx
-
Ha, oh it's definitely 64 bit! (see attached) :cheesy:
Don't know what the eicfg file is or does, but I've looked on the install disk you sent and there's no file of that name on it so I'm not sure whether the disks need re-doing or not - is there any other way to tell? It did run ok right to the end, something in the last stage seems to have upset it, but I was in bed at the time and it had rebooted by the time I saw it again. :sleep:
I'll leave the adapters as is then from the sound of it, unless leaving the 6to4 one on is likely to cause problems by being there :undecided:
Should we wait for Shane's input on trying removing the WSE/.NET framework thing, he may have more idea about that...?
-
The eicfg file ties the version down to what it is, but a Win 7 install disk has all of the versions up to Ultimate on it for that architecture (32 or 64bit but not both).
On reflection, I think I burned the ISOs on this laptop for http://www.tweaking.com/forums/index.php/topic,2949.0.html and Derrick was able to successfully do a repair install.
I think the ISO on this laptop is the newer Refresh edition that Digital River supplied prior to MS pulling them, but not sure if I downloaded the one on my other laptop earlier - memory !
I'll burn a couple of disks on the other laptop after running the eicfg utility on it and send you those.
That will be tomorrow's post now as I have to send my ISP's router back as it had me pulling my hair out last night and the rest out this morning.
I solved the problem by putting my own router on this morning, but initially thought it was a combo of the ISP router and Norton 360 blocking the Internet - we live and learn - the hard way :cheesy:
-
There goes my memory again -
As well as a couple of the universal disks, I also sent Derrick a spare Win 7 x64 Home Premium SP1 ISO which he could have used for the repair install.
I've had a dig around my stock and found another actual Home Premium one I can send you as well as a couple of fresh universal ones.
Gonna burn those universal ones now.
-
Yeah, know exactly what you mean about the memory! :cheesy:
Ha, so you think the issue is with the disks you sent then - were the 2 I got both the same? They had the same description on the case but I've only tried one, thinking the other was just a duplicate.
Is trying the WSE/.NET idea not worth a go then? Either way I'm not fussed, if you think re-doing the universal disks from a different download or an actual Home Premium one is the way to go then I'm more than happy to give one or both a try, whichever way you think is best... :artist:
-
So Shane's saying I can remove the MS ISATAP and 6to4 adapters then, fair enough, but do I need the Teredo tunneling one?
Yes you can remove it :-)
Windows will be reinstalling itself and so you dont need to worry about a lot of those things. The list you got mainly means those will be things that will need to be reinstalled after the repair install, thats why some of the things listed are hardware drivers for your phone and such. :wink:
Shane
-
Yes, those disks were the same - just sent you a spare.
The ones I'll be posting tomorrow will be one marked as Home Premium and two marked as Universal - you cannot have too many install disks as they can get damaged.
Give the Home Premium one a try first and hopefully that should work without a glitch.
You did run Belarc Advisor to get the vendor's generic key ?
-
Ok cheers guys
Yeah, I found and ran Belarc last year when I was having my many problems, at one point (more infact!) it told me my copy of Windows wasn't genuine and had to be reactivated so I've had it since then :artist:
Right, I thought they were the same, no problem, I'll have another go with the Home Premium one when it arrives and hopefully that will complete the last stage and repair everything it's meant to... :smiley:
-
Posted them off 1st Class Post this morning Tony, so you should have them by Friday going by the last rate of delivery.
-
Got them this morning actually Boggin, so thanks again and good on ya old bean! :artist:
Also uninstalled the WSE 3.0 .NET thing as it's apparently obsolete, and can always be reinstalled if I ever need it (unlikely), so a quick disk cleanup and recheck of the Win7 Upgrade Advisor is now completely clear! :smiley:
Now I'm just going to reboot, turn the AV & firewall off and then give the Home Premium disk a whirl, watch this space (in several hours that is, or probably tomorrow given the hour... ) :wink:
-
Don't forget to back up your drivers folders from Windows\System32 and then you can drop them back in after the install.
-
Ah ok, thanks, will do - don't think I've backed them up yet! :thinking:
It came up with an error actually saying it had to be rebooted due to system files having to be reset or some such, so I'm going to have to try again.... :undecided:
-
I can't understand why you are having problems with the install.
I think it was either last year or the year before when I used one of the HP disks to do a repair install to get back in and it went without a hitch.
If it said it would have to reboot I think it should have its own prompts to continue rather than having to start from scratch but....
-
No, neither can I, although I'm not overly surprised given the trouble I've had with the machine over the last 18 months (mainly with WU) :angry: but it actually gets worse - that was the second time I'd tried the new Home Premium disk - the first time it said it couldn't create a system folder or something with error 80070005, so I rebooted then I got that one mentioned above, anyway rebooted again and got it going this time, but when I came back to it it had bombed out Again, this time with error 80070017 (see attached)
I was wondering - do you think the original (failed) repair I did with the first Universal disk you sent has done something which is causing this repair disk to fail?? After that attempt I had extra folders on my C: drive ($UPGRADE.~OS, $WINDOWS.~LS, Windows.old) and had lost 2-3 Gb of disk space! Should I delete some/all of these before I give it another go - is there something that attempt has done which could be stopping this disk working, or something on the drive seeing as it got so close to finishing the repair? Just my thoughts, I'm not sure what else to do other than reboot and try again.... :undecided:
-
When it reverted from the previous failed install using the first disks, it would have restored your previous install from Windows.old so I don't think any corruption would have occurred from that, but I'm not sure if you should have Windows.old after a failed install.
The error 80070005 generally relates to permissions and access denied but a Google for 80070017 comes up with either a bad CD/DVD or DVD drive.
This results in some of the files not getting to the target HDD either because of corruption of the DVD or the disk player isn't reading the DVD correctly.
Before sending you the disks I booted up with each and performed an offboot sfc /scannow which executed without any errors, so I think the disks would be okay and I specifically put the HP one in between the universal ones to give it added protection - but you could try the reinstall with either of the other disks which I ran the eicfg removal on.
CD/DVD drives can go at any time and to eliminate yours as the cause, if you have a 4GB Flash drive you can create a bootable USB from the DVDs by following the DiskPart steps in http://www.wikihow.com/Make-a-USB-Bootable
-
Hmm, well the DVD drive seems to be ok, and the disk looked fine, but I tried it again after a reboot and it got stuck "Copying Windows files" at 65% and eventually gave the 80070017 error again, so I presume it's stuck at the same place again and can't copy something from the DVD.. :sad: oh well.
Not one to give up, I tried one of the 2nd Universal disks, and this one differs from the 1st (pair) in that it asked me for the version of Win 7 to install, which the first one didn't, so I chose Home Premium and it seems to be running ok :smiley: well the first one did as well, right up to the last stage, so who knows! Anyway it's on the second stage right now, gathering files, settings & programs, and hasn't stuck yet, so fingers crossed (Again!)... :undecided: :sleep:
-
The reason the universal disk asks which version is because it has all versions on there and doesn't nail it to the original Pro version that it once was after the eicfg file removal.
The HP disk would be the same if the ISO had the eicfg file removed, but I can't understand why that isn't working.
If you get a chance, try using that DiskPart tutorial to create a bootable USB from the HP disk to see if a repair install will work from that after creating a full system image.
-
Ah I see. not sure why the HP disk wasn't working but the second Universal disk has failed as well :sad: different error to the first Universal one though (see attached) - no specific error, just a generic "Can't continue, reboot, get updates" message.
Don't have a small USB stick I can use to create a boot ISO from just at the moment, could maybe get one next week some time... Sigh, any more ideas other than just rebooting and trying again (although that's always worth a try) :blank:?
-
So why not do what the message says ?
It may need some of the updates as pre-requisites.
The disks can't have been bad burns as I'd just had a new DVD drive fitted to the laptop that I burned the newer disks on, and at least that error message seems like progress.
-
Ha, well, because "doing what the message says" ie. the getting updates bit, is the main reason I'm here in the first place! That and the missing package files from the pre-scan - trying to update just sends me round in a "Windows Update needs to install an update" loop with the 80073701 error, so if installing an update is a pre-requisite of getting the repair install upgrade to work then I appear to be stuffed! :sad:
Gave it a go anyway, got the usual messages as attached. I'll have a go with PortUp, PatchMyPC and APUP (and any others you might know about! :wink:) and get back to you, but I'm not holding my hopes up as they very seldom manage to get any updates installed, apart from the odd Defender definition update, .NET update, and Very occasionally :shocked: an Actual Windows or Windows Security Update!! :omg:
-
Perhaps it really is time to consider that factory reset.
-
Yeah, I kinda thought you might say that! :tongue:
It might come to that, but all is not lost yet, however, as yesterday I managed to install a few updates through both PortUp and Autopatcher, and then tried the 2nd Universal disk again - same error as last time (non-specific, updates required etc). Then today I'm running the second of the second lot of Universal disks, currently on the Gathering files section (no harm in trying them all!), and just happened to look at the Windows Update Control Panel (which earlier was showing the usual red warning and Check for Updates message), and lo and behold it's showing the Download and install updates for your computer message (see attached) - 32 important and 2 optional!! This is the first time I've seen this "working" or at least displaying properly in a loooong time! :smiley: :smiley:
I'm reluctant to press install though as the Upgrade is still running and I want to see how far that gets, but something with the either the duplicate install disk, the alternative update programs or one of the updates installed (I got 4 on yesterday :artist:) has somehow got the MS WU prog to work again, so I'll carry on checking the progress of the repair and post back, fingers crossed...
-
Windows does seem to have a way of repairing itself with a little help, although I wouldn't have expected to get a prompt for WUs in the middle of an OS install, unless it's gotten the main bits in.
If it does baulk again, check to see if the WUs are still there to download as the key may be in those.
Perhaps you should have persevered with the first disk's prompt to reboot, but it's starting to look good.
-
? Not sure which reboot prompts I haven't followed - thought I'd rebooted every time I've been told! :confused: maybe we've misunderstood each other, but either way things are definitely improving, although it has bombed out again but right at the end of the upgrade this time, nearly 100% of the way through the last stage of transferring files and settings, dang. :thinking:
On restore to original version though, the updates are still showing in Control Panel WU, so that's a positive! Trying to go through some of them now, a few at a time, as I tend to find (in the past!) that asking it to do a heap all at once is often what caused problems, so I'm doing it steadily just to see. If I can get a few more on then maybe one of them will just help the repair upgrade over that final hurdle :smiley:, or maybe I won't even need it! :wink:
Quick update (arf!) - 1 of the 3 .NET updates was successful - the most recent, the other 2 error 80073712 (corrupt CBS). Just trying a handful more Windows & Security updates now, see how those go... 4 of 5 have installed! The 1 failed with 80073712 again, time to post, reboot & try a few more.. :artist:
-
When you get a fail error code in WUs do you ever use the Help section for that code to see what it says ?
-
Oh yeah, if I don't recognise it, but I've seen 80073712 loads of times and know it's related to the the CBS/registry being corrupt. MS says SURT or SFC to fix the error, but we've tried those unsuccessfully already during this process...
My joy at geting the WU working again was shortlived however, as on reboot I got a BSOD with 9e error, then when it wouldn't boot into Windows I went into the install disk to get to the recovery/repair menu, and on running startup repair I got the message 'Windows Codename "Longhorn" Preinstallation Environment (recovery) Path $WINDOWS.~BT\Windows Partition =E: Copy saved as C:\Boot\BCD.Backup.0002'!!! Like, wth does all that mean??? :omg:
I'm currently running a chkdsk/r on my E:\ drive, which has found some bad clusters to replace, but other than that I'm not sure what to do other than try reboot again once it's finished, and no idea at all on the strange repair message! :confused:
-
I haven't a clue what that error is either, but as it says Backup.0002 would suggest it has done it before.
I'm a bit confused as to which drive is your active drive and which you are installing Win 7 on.
A chkdsk /r doesn't repair bad clusters, it repairs what files it can and relocates them to the good areas of the disk and ropes off the bad areas so nothing else can be written to them.
Once you get bad clusters it is only a matter of time before the drive fails completely.
-
It's a new one on me as well! If it has happened before then I'm certainly not aware of it or what it means, I've had a look in the C:\Boot directory and there's no files of that name, either .0001 or .0002, unless it's in the offline C: (which isn't visible in Windows, it's the Dell first boot/diagnostic partition I believe).
In Windows my OS is C:\ - is this what you mean by "active drive"? All my progs, settings and OS are there, so I presume that's where the installation is going, and I also have an E:\ partition where I keep all my data and libraries. When booting offline or by CD the C: becomes D:, the hidden one becomes C: and the E: stays as is. In addition to the new folders on my C: drive, there's also a WINDOWS.~BT folder on my E: drive with several folders in, over 12,400 files and taking up 2.3 Gb of space!! :omg: In contrast, the UPGRADE.~OS folder on my C: drive has only 400+ files and 98 Mb of space, not sure why it's put the other on my E: drive... :undecided:
Anyway, the chkdsk has repaired some errors on my bitmap volume on E:, if the suspect bit of disk is now marked as "bad" then hopefully it can't cause any further errors? Although I know what you're saying, potentially it could spread and the HD could go at some point.. :cry: For now though it's back up and running ok again, so I'm checking out the update situation again with the hope of getting as many as I can on and then giving the upgrade repair another shot!
-
With the time you have spent on this, you could have done a factory reset by now :lol - but with bad sectors that could have had problems of its own had they gone unnoticed.
As for the partition/drive letters changing, even though the OS is in C: - when doing anything outside of Windows, Windows can see the OS in a different partition which is why when executing the offboot sfc, you need to make a note of the location or run the command bcdedit |find "osdevice" - so I suppose if one letter gets changed then the rest will probably move up, but I don't know why.
At least you have everything backed up externally should the drive fail.
-
Ha yeah, you're probably right, but I naively thought that the repair install would be quicker, easier and less hassle than a full factory reset or clean install, little did I know :thinking:
Anyway it's all moot now as I've managed to get the repair install to (finally!) work! I can barely contain myself!! :wink: I've had a busy week but after the last failed attempt, I got a few updates on using various methods but still no joy with the upgrade. I then decided to re-run the MS SURT, followed by the All In One Repair in safe mode, after this the WU were still working and showing 28 + 3 optional but none of them would install (usual story). I also changed the owner of the CBS registry key back to Trustedinstaller (from Admin) after something I read of yours Boggin which prompted me to check it, as I've done that MSI registry key fix myself in the past and it was all there ok apart from the Ownership.
Then having exhausted my ideas of what to change I thought it might be time to try the upgrade install again, firstly with the Home premium, which again got stuck, so I tried one of the first pair of Universal disks again and let it rip and went right through to the end! Holy *&$£ man!! :artist:
I'm just in the middle of trying to figure out what I need to do now to get everything working normally again and back to how it was - so far I can see my desktop themes are different, appearance is different (I had aero and other effects off before for better performance), Avast has been turned off for some reason and won't start again, either with the shortcut or with the Action center button - it says the side by side configuration is incorrect! Any idea what I need to do to get it going? The Windows Features box is now visible again after a long time not working, woohoo, and WU appears to be still working, but failed on error 8024001B when I first tried it (update needed to update!), so I've rebooted and tried again, currently "Checking for updates........). Also when my Glasswire connected the first time it came up with a big list of about 10 different items which have all been removed! - do these need replacing or are they all redundant? (I can write the list down if needed, network adapters/drivers by the look of it)
Other than those few niggles all looks to be good, hopefully I can ge the AV back on now and get the WU's all up to date and then the job's a good 'un!! :smiley:
-
If you backed up the Drivers folders from Windows\System32 before the repair install, then you can drop them back in and that should resolve some problems.
If you are able to download Windows Updates then your Internet must be working okay and it can drop some drivers in for you to keep you going.
-
Yes the internet seems to be working ok - I've just updated SuperAntiSpyware defninitions without any problems, so I'm now going to try and update using WU - it's found 183 Important and 11 optional updates to install!!! :omg: :shocked: :cry:jeeez, just going through the list and trying to figure out which ones to install first as I'm out later and can't leave it running/connected, so maybe I can get a few of the smaller/more important ones on before I go...
I did wonder about the drivers I backed up - do I just merge the folders and replace any existing drivers in Windows with the ones from my backup? Not sure of best way to do it. Will this sort my Avast issues out? Tried it again but it gives the same error as before. Also tried running an SFC and it says beginning verification phase then stops after a second or two with Windows Resource Protection could not perform the requested operation! :sad:
-
Have a look at the optional ones first as MS is pushing some to ease upgrading to Win 10 and if you have no intention of taking up what looks like a proposed free upgrade, then you can hide them.
The Optional ones I have hidden are -
KB2952664
KB2990214
KB3013531
KB3020369
KB3045645
When you drag & drop the drivers folders back in, you should be able to click on the name System32 and will probably get a prompt to merge.
I wonder if that sfc /scannow error is because of the bad sectors - check to see if the command will run in Safe Mode.
You may have to reinstall Avast.
-
Ok thanks for that info, just trying to get all the WU's on first before I put the drivers back on. Unfortunately I seem to have hit a major snag and now my machine looks rather screwed! :sad:
I got about 50 updates or so on, then after a reboot tried to check for updates and it threw up error 80080005 (something to do with corrupted dll's which can be sorted by running SFC) and couldn't check. Tried the SFC and it gave the same error (couldn't perform the requested operation), so I remembered your comment about trying it in Safe Mode and thought I'd try that, after first trying it in Repair/offline mode. Booted into repair mode, Startup repair couldn't find any errors to correct, then tried an offline SFC - said it couldn't scan due to a pending reboot! :confused: Tried a reboot but made no difference. Anyway gave that up and went into Safe Mode and then discovered all the text is missing from Windows! The Users names are missing from the logon screen, the button which says Switch Users is blank, and once I go into Windows all the desktop icons are blank! The Windows orb also doesn't do anything. I've also tried going back into Normal mode to see if it's just Safe mode but it's the same in either. I got task manager up using the hotkeys but there's no menu or options on it, although the tabs all show text on them (programs running, processes running etc)
Any idea what could have caused it or how to get it looking ok again? Literally the only thing I've done is install WU after the Upgrade - I've just tried doing a System Restore to prior to the last set of updates and it's failed with )x8000ffff, so I'm going to try a different one (there's only 3, the Repair/Upgrade and 2 WU restore points, so I'm limited but I'll try them all), unless anyone's got any other ideas on what the hell might be wrong with it.... :rolleyes:
-
Found this possible fix in my toolbox for the pending reboot which you could try.
Boot with either the install disk or into Safe Mode with Cmd Prompt to rename the pending.xml file
takeown /f x:\Windows\winsxs\pending.xml
Ren x:\Windows\winsxs\pending.xml pending.old
exit (to close the command window if booted up with the install disk)
Shutdown /r (if in Safe Mode with Command Prompt which will effect a reboot)
Reboot and try again.
As the Start button isn't working and everything seems to be screwed up, sometimes a cold boot can resolve.
That is where you disconnect the AC and remove the battery then hold the power button in for ~30secs - plug the AC back in and see how that performs, but if you have to boot up with the install disk to get to the command prompt, then run chkdsk c: /r after to see what that reports.
I think you said it gave the partition as C but use whichever partition letter bcdedit |find "osdevice" gave instead of C as required.
I can't find 0x8000ffff in https://support.microsoft.com/en-us/kb/938205 so don't know what that one is for.
-
Thanks again Boggin, but the immediate panic is over! :smiley:
No idea what happened to the machine, but even though all the restore attempts said they'd failed with that same 8000ffff error code, after the last one I rebooted (back into normal mode) and a pop up message said that the system had been successfully restored! It was the oldest of the points however, the repair install one, so now it looks like it did after the repair with everything in fresh W7 mode again, but of course I'm back to having all 183 important updates to install :omg: so I've bitten the bullet and just kicked it off with them all ticked! :cheesy: see what that does.
I did also do a cold boot/reset and a chkdsk /r on both C: and E: while I was in repair mode before the system restore, and no errors were found, although it did correct the volume bitmap on one of the drives...
Checked on the updates not long back, it was on 18 of 181 (for some reason not all the 183 were ticked so I left the 2 odd ones off), and there was a message box saying that the .NET framework 4.5 was being repaired and to leave setup running the NetFxRepair until it had finished! I presume one of the WU has kicked this off? Nothing else was running.. It's not the first time I've had .NET framework issues, having run the repair tool in the past to try resolve problems, so whether this was what caused the earlier weird text display problems, or whether it's a "new" update installation issue I don't know. :thinking: The repair's completed now and it needs restarting to get the .NET working correctly again, but as the updates are running along nicely (55 now) I think I'll leave it updating for the minute and turn it off when I go to bed, hopefully interrupting the updates won't cause problems, we'll see... :undecided:
-
What did the chkdsk /r report for bad sectors ?
I think I would have just set the laptop to High performance and left on overnight for the WUs as I prefer not to disrupt those.
When you restart it, that will effect the .NET Framework fix and may aid the WUs.....
-
It didn't report anything for bad sectors, just said it had made a correction to the bitmap volume.
It's an all-in-one desktop (monitor with contained HDD etc), not a laptop, and I tried to leave it on Sleep mode so I could continue straight on this morning, but when I came down it was still on, and the updates had moved on to 150! Not sure how without my phone and no internet, but there you go - I reconnected my phone, hooked up the net, and it appears to be stuck on 150 (been on 3033929 for about half an hour now!) so I'm probably best stopping the installation and rebooting I guess, and seeing how the restart and continued updates go.... :undecided:
-
WUs have to download before they can install, so if they've all downloaded and it's in the install phase then it wouldn't need an Internet connection to continue.
-
Ah I see, that would explain it! Not sure why it ignored my order to "Sleep" though, but it seems to have successfully installed most of the 150 WU it got up to before it stuck, but then it had a wobble when I rebooted and BSOD'd with error e9, then eventually started ok.
None of the updates are showing in Update History (it's blank), but when I go into Installed Updates there are 147 MS Windows showing, only 2 of which were there after the Upgrade, so the majority of them have gone on, which is promising :smiley:
Now to try get the rest on.... WU is telling me to restart to install important updates, but I just have done! It's in a restart to install loop I'm afraid, let's try rebooting again then...
Oh and before I forget - have tried to rename the pending.xml file while in Windows, and it won't let me do it from either Windows explorer (says Permission needed but then won't allow it) or using your dos commands (says Access is denied), so the SFC scan Still won't run - now saying system repair pending which requires reboot to complete, rather than Windows Resource Protection could not perform the requested operation, so still at a loss with that one.... :rolleyes: :sad:
-
I think you should cut your losses and opt for a factory reset. :smiley:
However if you ever get past the WUs, here is a possible fix for that pending error for sfc /scannow.
It isn't my fix but comes from a reliable source and because I cannot find it in my toolbox, I'm going to have to type it out in full myself from a print out I took of it.
Probably best to do this booting up with the install disk to navigate to the RE and select Command Prompt as it isn't giving you elevation, although it can be done by booting up into the Advanced Boot options and select Repair your Computer.
Anyway, at the command prompt try this dism command -
dism.exe /image:c:\ /cleanup-image /revertpendingactions
exit
Then Restart and try the sfc again.
If that doesn't work then from the RE Command Prompt again enter these commands and follow the other steps, but as they involve working in the Registry - probably best to create a restore point first.
c:
cd c:\windows\winsxs
ren pending.xml pending.old
regedit
Highlight HKEY_LOCAL_MACHINE and from the File menu click on Load Hive
The select Hive location (sources) will open then browse to C:\Windows\System32
Locate the folder C:\Windows\System32\Config\Components and click to select.
When you are prompted for a name, type Offline_Components (not sure if you have to press enter after that, just copying from the script).
You will now see Offline_Components - expand the + and locate then delete the following registry keys -
HKEY_LOCAL_MACHINE\Offline Components\AdvancedInstallersNeedResolving
HKEY_LOCAL_MACHINE\Offline Components\PendingXmlIdentifier
Go back to Offline_Components - highlight it then from the File menu select Unload Hive
Close the registry up and reboot
See if it will let you run the command prompt as an admin and enter -
net stop wuauserv
cd %systemroot%
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv
That rename command will clear the WU history.
Off to have some trough now and then back to see if I can sort out my other laptop - long story so won't go into it.
-
Ha, yeah, I know what you think I should do, and you're probably right, and a large part of me agrees with you too... I know I'm most likely just delaying the inevitable, but the persistent (aka stubborn! :wink:) old part of me is determined to get this machine back in good working updated order without having to re-install all the 100+ programs on it, and the repair install HAS finally been successful, so now I'm just hoping the updates follow suit and do their thing accordingly :smiley: I'm nothing if not hopeful.. At some point, when I ever get round to (or am forced to!) replacing the HDD, then I daresay I'll do a clean install, till then I'll do my best to keep this build up and running :tongue:
Anyway, from the RE I managed to rename the pending.xml no problem, then ran the offline SFC, and lo and behold it ran - and not only that but didn't find any integrity violations! Never saw that before the repair install, so Bingo on that one!
I'm assuming now that solution worked that I don't need the dism /revert command as well, or the HKLM registry tweak?
So, onwards with the updates, if it will let me - it got stuck opening up the WU page before on the Control Panel, and Autopatcher also got stuck installing critical updates as well before I switched it off in disgust, so let's see if restoring the SFC has done anything to the WU, if not I'll try that last bit of your message script and report back... happy troughing and good luck with the laptop!
-
Ok, so the latest on my machine, which is a mixture of both good and not so good news... :rolleyes: (surprise! :wink:)
On the plus side my machine is now up to date, seemingly, although every time I select all the Important updates and get them on there appear to be more next time I manage to check again! :confused: weird, anyway, at least they're on, including IE11 which would never install before, just finished installing a couple of IE11 Security updates and a Windows Defender definition update which showed up after getting all the others on, then see if that does them all, again, with a further check......
Windows Features is still working, a bonus, and Shane's AIO Repair pre-scan is showing clear with No errors at all on the Package files, reparse points or Environment variables, which is super great!! :artist:
So there's plenty of positives, thanks to all, however, there are still issues with updating I'm sorry to say. Every time I've managed to get any updates on, without fail, the machine would configure and restart ok (apart from once where it said Reverting changes), then upon rechecking it would throw up error 80080005 and not be able to check due to updates pending; also there would be a pending.xml present and SFC scan would not start due to reboot/repair pending, so I've had to go into Repair mode every time and manually rename pending.xml (can't do it within Windows! :angry:), then SFC scan would work, then I could reboot back into Windows and re-check successfully for updates, where it would always find more! I now have 4 or 5 renamed pending.xml files - do I need to keep them all? There's also a reboot.xml as well, what about this one?
Phew, also, and this may or may not be related, Windows Explorer keeps crashing, Regularly! Always after a restart when I open Control Panel to check for updates, and sometimes in the middle of just doing stuff (updating, browsing, etc) later as well. Plus the SFC scan is now finding file corruptions and is unable to fix some of them, which is how my machine used to be before the Repair install! :sad: I've attached the CBS.log (which is now tiny after the repair! :smiley:), but I can't see anything obvious in it pointing to which file/s might be at fault, and as I said the pre-scan is showing clear, so any ideas on what the problems might be with the Explorer, the SFC scan corruptions and the dodgy update/pending.xml loop problems please?
Tweaking.com - Windows Repair - Pre-Scan
Computer: T-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
Started at (15/05/2015 12:22:59)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (15/05/2015 12:22:59)
No problems were found with the Packages Files.
Files Checked & Verified: 3,695
Done (15/05/2015 12:32:30)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (15/05/2015 12:32:30)
No problems were found with the Reparse Points.
Files & Folders Searched: 284,359
Reparse Points Found: 92
Done (15/05/2015 12:38:41)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (15/05/2015 12:38:41)
No problems were found with the Environment Variables.
Done (15/05/2015 12:38:41)
--------------------------------------------------------------------------------
Done (15/05/2015 12:38:41)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Done (15/05/2015 12:38:41)
Scan Complete - No Problems Found!
-
What does a chkdsk in read-only mode report now ?
Can't remember if we've already gone through this but you just enter chkdsk without any parameters for the read-only mode.
Edit - Forget this, just seen your response to the other thread regarding SFCix.exe
So how are the WUs going since that sfc fix ?
-
Yeah, sorry Boggin - forgot to update my own thread with a fix I've posted in a different one! :rolleyes: ha.
Chkdsk is still showing clear, for now, although it does sometimes make corrections to the bitmap volume, but no more bad sectors lately. The SFC is now clear again thanks to the SFCFix, and the updates all (finally!) managed to install ok after several attempts, and those last 3 didn't require a reboot (maybe as they were only IE & Defender updates, rather than Windows or Security updates). A check after those showed no more Important updates to install, just the 4 optional ones I haven't added, and a green MS tick message!! Yay, Finally!! :artist:
My only question now relates to all the renamed pending.xml files - do I need to keep them? And the reboot.xml in the winsxs folder as well? And I'm a bit wary that every time the monthly updates come around that I'll be in the same boat having to rename the pending.xml and do a double (or more!) reboot and recheck every time - any idea what's causing it to do this or how I can stop it?
Other than that, and still having the drivers to copy back on again (which doesn't seem to be causing any problems!), I'm tempted to mark this thread as [Solved] now - do I just amend the title in the reply to do this? Cheers
-
I'd wait for Shane's advice on those renamed files, although I would expect you'd only need the latest pending.xml.
I can't understand how chkdsk /r reported bad sectors but now it shows 0 KB in bad sectors as once they are there they don't go away.
-
No I meant it hadn't found any more bad sectors! There is a small area (several kB, forget the exact number) attributed to bad sectors, but none extra added to it since I last mentioned it had found some. :tongue:
Okay, I'll wait for Shane's advice on the pending and reboot xml files, and many thanks for all your help (and disks!) mate, appreciated :artist:
-
You're welcome but there is something you can help me with.
I've never had to attach sfc details to a post, so how do you do that ?
-
Not sure what you mean by "attach SFC details to a post"!? :confused:
Ha, all I do is either copy and paste from Notepad/command prompt/whatever into the body of a post, or if you mean add a file attachment then I just click the "Browse" button next to the "Attach:" thing underneath the reply box (see attachment! :wink:) and that opens up a browsing/exploring window for you to find the required file(s) - is that what you're referring to??
-
Wow! 9 pages so far in this thread, I was just speed reading through and noticed you are waiting for some advice from me, I am also answering all the other posts right now as well.
If you dont mind what posts in this thread should I go and read carefully to answer your questions? I also noticed you said you did find some bad sectors, the moment you find even one bad sector it is normally a good idea to replace the drive because it is only going to get worse.
All hard drives have a small batch of sectors set aside so when a bad sector is found then it is remapped to a good sector from one of the spares, by the time Windows finds bad sectors that means that all the spares have been used up and there is no more spares to remap to. So this also shows that the bad sectors are growing and will only get worse with time. :wink:
Shane
-
Yes, that was it Tony.
I would normally copy & paste the Notepad text but I was looking for how to just add the link.
Unfortunately, I'm getting the error that it cannot find findstr so the Notepad file that opens is empty.
-
Ah I see, can't believe you haven't attached a file to any of your 1100+ posts before though! :omg:
If the CBS.log (I presume?) doesn't contain the string typed inside the findstr [] then it won't pass anything to the file created - I've had this before. Either that or the syntax of the dos command isn't quite correct so it's not running as expected and then not returning anything even though it's there - what's the exact syntax of the command you're using?
-
Hi Shane. yeah, sorry it's been such a looooong process and long-winded thread! :rolleyes: but it's been worth the drag and I'm very grateful to yourself and Boggin for all the help and advice offered :artist:
There were a couple of outstanding questions though - to cut a long story short, as I know you're a busy guy with a lot on your plate right now, following an (eventually!) successful repair install the system is now fully updated and your pre-scan has come back clear for the first time ever. SFC is also clear (after a late fix for some new errors using a different program). To save rephrasing what I asked Boggin, which he said to wait for your advice for, I've copied the following couple of paras from my earlier posts, so if you get a minute I'd be interested in what you think the problem and solution might be, cheers :smiley:
"Every time I've managed to get any updates on, without fail, the machine would configure and restart ok (apart from once where it said Reverting changes), then upon rechecking it would throw up error 80080005 and not be able to check due to updates pending; also there would be a pending.xml present and SFC scan would not start due to reboot/repair pending, so I've had to go into Repair mode every time and manually rename pending.xml (can't do it within Windows! :angry:), then SFC scan would work, then I could reboot back into Windows and re-check successfully for updates, where it would always find more! I now have 4 or 5 renamed pending.xml files - do I need to keep them all? There's also a reboot.xml as well, what about this one?
My only question now relates to all the renamed pending.xml files - do I need to keep them? And the reboot.xml in the winsxs folder as well? And I'm a bit wary that every time the monthly updates come around that I'll be in the same boat having to rename the pending.xml and do a double (or more!) reboot and recheck every time - any idea what's causing it to do this or how I can stop it?"
-
It's not often I need to ask for help as I can usually find a fix and I would have just normally copy & pasted the file.
The command I used was findstr /c:"[SR]" Cannot %windir%\logs\cbs\cbs.log > 0 & notepad 0
I'll have to check the sevenforums tutorial for sfc /scannow.
The reason I ran the sfc was because of what KB3022345 was doing http://www.infoworld.com/article/2922324/microsoft-windows/windows-usage-tracker-patch-kb-3022345-triggers-sys-file-corruption-which-sfc-is-unable-to-fix.html so while I had uninstalled the KB because I kept getting errors that the Diagnostic Tracking Service had stopped, I decided to reinstall it and run a sfc /scannow and got an identical report to the one you had posted.
That would tend to suggest your errors were a direct result of installing KB3022345.
Anyway, I ran the SFCFix.exe and that sorted mine out as well.
I've been thinking about restoring back to before I reinstalled the WU but have checked Reliability history and there's no repetition of the Diagnostic Tracking Service error so perhaps it was the file corruption it had caused which was also responsible for the error - I'll check Reliability history again tomorrow before I make my final decision.
-
Ah yes, I remember you posting that earlier in my thread - take out the "Cannot" and it will work fine! :artist: not sure where it's come from but it shouldn't be there and gives an error which goes when you take it out. If the notepad file generated is still blank then whatever is inside the [] ("SR" or anything else) hasn't been found
I've noticed KB3022345 on my installed updates list, but it did fail initially and reverted changes on one occasion before it installed, for whatever reason - looks like it might be one of MS's notorious dodgy updates if it's done the same on yours. Glad the SFCFix could be of help anyway - nice to be able to repay all the help in some small way :smiley:
-
Did you run another sfc /scannow after the SFCFix.exe to see if it was clear of corruption ?
Removing cannot didn't produce anything in Notepad either.
-
Yep, ran SFC again yesterday and it was still clear :artist: although as no more 'proper' Windows Updates have been installed since I ran the SFCFix (just a couple of IE security updates and a Windows Defender definition) then this is hardly surprising - the acid test will be next month when the new patches are all released! :undecided:
Is yours still clear after the fix?
If taking the "Cannot" out hasn't returned anything then the "SR" isn't present in the file you're searching (CBS.log etc) - I ran it on mine and it opened a blank Notepad file (but without the DOS error that the "Cannot" produced), but then my CBS.log is tiny now after the repair and a manual search for "SR" didn't find anything either! I think that's the 'issue' as such - just the fact that it isn't there to be found :thinking:
-
Restoring to just prior the WUs still produced files it couldn't fix and got the same with an offboot sfc.
Had to restore back to about a week before WUs before sfc /scannow was able to repair found corrupt files.
I've reinstalled the WUs less KB3022345 and thought all was well until I noticed my sound wasn't working.
No alerts or red crosses on the icon and the Realtek says it's working properly, but still getting Failed to sound test tone.
I'm not sure when this started so I can only assume one of the WUs is responsible - time will tell, but I'm not going to fight with it until tomorrow.
-
My only question now relates to all the renamed pending.xml files - do I need to keep them? And the reboot.xml in the winsxs folder as well? And I'm a bit wary that every time the monthly updates come around that I'll be in the same boat having to rename the pending.xml and do a double (or more!) reboot and recheck every time - any idea what's causing it to do this or how I can stop it?"
You can remove these, in fact my repair windows updates does the same thing and more, the more I have dug into Windows updates and how they work the more I realize how big of a mess it is. You can tell hundreds of people at MS have had their hands in it and so it is a big mess.
After all it was reported MS had a 110 programmers just for the start menu and taskbar alone for Windows 7. Now imagine how many they had for the updates. I read one time where Windows had something like over 10,000 programmers to make it. Not sure how accurate that is but it does explain why things break as easy as they do in Windows. EVERYTHING in Windows depends on something else, so when one thing breaks it creates a domino effect and then the horrible type of error messages give the user or tech no clue on where down the chain the problem is.
To many damn fingers in the pie!
Shane
-
Ok, thanks for that Shane - in that case I'll delete them all :artist: I have 6 of them now - I checked for updates again yesterday and afterwards there was another pending.xml and SFC wouldn't work! :sad: Is it going to do this every time? That's my worry going forward - deleting them isn't the issue but the fact that they're getting created every time I check for updates (I'm guessing!) and then stopping SFC from working or further checking for updates. It wouldn't be so bad if I could just delete them in Windows but the fact I have to go into Repair mode to do it makes it that much more of a pain. Is there any way to stop it doing this?
Other than that though I think I can say it's cured pretty much as the system is up to date and working ok apart from this problem - right now though I have much more pressing issues. First off Malwarebytes found a trojan (Trojan.Zekos.Patched764SP0infecting rpcss.dll+) which it couldn't quarantine, so I rebooted into Safe mode and ran it again and this time it said it had been quarantined. The file is still there however, in Windows\System32, along with rpcss.dll - I've uploaded both to Virustotal and it says they're clear, but MBAM was still picking it up as an infection! :confused: Avast and SAS had both missed this and it must have appeared since the Repair install as I scan with MBAM every week. I also ran RKill, RogueKiller, AdwCleaner, HitmanPro and Spy Hunter and all were clear (ish, apart from some adware or PUPs, but no trojans)
I was in the middle of an ESET scan when the machine hung, then crashed with a BSOD, and now it won't boot at all! :cry: it goes into a Startup Repair loop which it can't get out of - I've tried going into 'Last known good configuration', Safe Mode and others through the F8 key and every time it goes back to Startup Repair, which then Can't repair! Problem Signature 07: Corrupt Registry is showing (although it was fine before and the last SFC scan was clear!), and the Repair scan details Root cause found says 'Startup repair has tried several times but still cannot determine the cause of the problem' (13 repair attempts now)
I have managed to run chkdsk on both D: (the OS) and E: (my data) and d: is coming up clear, so why it won't boot I've no idea, but E: is hanging on trying to correct an index entry on a file. An earlier chkdsk on e: which Did complete said insufficient space to correct the entry errors, yet there are 55Gb of space Free on E:! :omg: SFC can't run, Unable to start, so as it won't boot or complete a repair I'm unsure what else to try - any ideas? And should I start another thread for this or keep it here? (and I do realise it's probably time I got a new HDD but it's not an option just at the mo, if this one is cooked then I do have a portable one I use for my backups that could be of use short term.... :tongue:)
Cheers
-
Well I found a few thing son that one
http://www.bleepingcomputer.com/forums/t/533200/rpcssdll-is-infected-with-trojanzekospatched/
and
http://www.malwareremovalguides.info/zekos-malware-infection-removal-guide/
But the fact the system wont boot and it says the registry is corrupt means you are not going to be able to get back in there without reinstalling unless you had a registry backup. (The registry could have been in the middle of being written to when the system crashed, thus corrupting it since it didnt finish writing, this is also the main reason you are never suppose to just turn off the system without shutting down first) By any chance do you have any registry backups done with my registry backup program? My Windows repair uses it to make a reg backup before the repairs and you can also use the program by itself as well.
If you do have a registry backup from my program then you will be able to restore the registry from it. I made a few videos showing different ways to restore the backup even if you cant boot into windows :wink:
http://www.tweaking.com/articles/pages/tweaking_com_registry_backup_online_help,3.html
Shane
-
Thanks Shane. Yeah I already found those links, and a couple of others, which is all what I was in the middle of when it crashed :sad: It probably has done something to the registry while scanning - I had two running before it crashed, so something's obviously caused it to fall over v. not savedthe regisrty correctly as you say.
Anyway, I do have backups from your AIO repair, but I'm not sure if they're from before or after the Repair install - I'm guessing before as I don't think I've run it since (apart from the pre-scan which came back clear). Also I can't view any of those videos on my laptop to see how to do it! It says I need a plugin, but I'm not sure which one as I have Flash player and watch youtube on it regularly :confused:
I have got my machine going in the past by copying the 'system' file in the registry hive from the Regbackup to Config folders in System32 - is that what you're video shows, or similar? I'm currently in a dos prompt in the Repair environment so let me know what to do please and I'll give it a shot :smiley:
-
Those are videos on youtube so it should show them to you and normally it is in flash. there is a setting you can also set on you tube to tell it you want to watch videos in html5 instead of flash.
You will also notice I do have the youtube link for each video right above the video itself.
Shane
-
Ah, I see - the youtube links, great! Don't know why it won't play on your tweaking page, it plays fine on youtube :confused: the only problem is the video is so low res and the dos prompt picture so blurred that I can't make Anything out on it! :sad: I can hear your voice fine and see the cursor moving around but can't read a thing... Any chance you could write it down and "talk" me through it here please?
It sounds similar to what I've done copying files from the Regback, but I heard mention of a .bat file and I don't know where to find the Tweaking files, I'm guessing in the Program Files or (x86) somewhere, if you could point me in the right direction, thanks.. :artist:
-
Youtube shows the video in different formats, click on the gear icon on the video and you can increase the quality :-)
Shane
-
D'oh - jeez I'm thick sometimes - forgot all about the quality settings on youtube - probably 'cos I never touch them. Anyway I can view everything now, thanks, the only problem is that the latest backup I've done, as I thought, was from the 7th May ie. before the Repair install which was on the 9th. I'm guessing that means I can't use it? Is copying any of the hive from system32\config\regbackup an option as I've done previously?
-
I dont know how that would do, I wouldn't use that old backup, and as for the backup in the config folder, check the date on it and see.
Once you get back up and running you may want to have my registry backup program installed and set to make a backup at every boot :-)
Did the error you got at least say which registry file was corrupt?
Shane
-
No it didn't say Shane, it was just a details pulldown on the Startup repair under the Send/Don't send box, which when you looked at it gave a list of about 10 bits of info like the OS number etc, the 7th just said "Registry corrupt" but no further explanation anywhere :sad:
The backup in the config/regbackup folder is from the 9th - I presume created at the time of the Repair install? Looking at the 5 files, and comparing them to the 5 in the Config folder, the only one that's changed the date/time stamp is the Software file - the others are all identical in both folders. Should I try backing up the Software file and copying the regbackup version?
PS - I do have your registry backup program but haven't used it since I first installed it last year or set it to do anything automatically, my bad in retrospect... :sad:
-
Well just make sure to save the current reg files now in the config folder, then play around with replacing them with what ever you like and see what happens. Worse comes to worse you can copy the originals back :-)
Shane
-
Hmm, well I've backed up the Software file and copied the Regabckup version in, and it's made no difference - just goes back into the Startup repair loop which can't repair! Still saying Problem Signature 07 Corrupt Registry; Problem Signature 05 ExternalMedia - any ideas on that? Not sure what else I can try as the other Regbackup files are all the same as the ones in Config..... :rolleyes:
-
I havent had that problem so I dont know anything off the top of my head. A fresh install might be needed since the repair install still had some left over problems anyways.
Shane
-
Ok, thanks. You may be right, that may be the final solution - I can't get it out of the repair loop at the moment and have tried several fixes I've tried online, to no avail. Currently running a scan from my Seagate tools repair disk while I plod on googling possible causes and solutions, joy.... :rolleyes: :cheesy:
If anyone else has any experience of this problem or knows what to do or try feel free to jump in and let me know! :tongue:
-
If the registry is shot there is no way to recover except from a backup, so since you dont have a good registry backup, backup your important files and do a fresh install, when you go through the install and it gets to the point where it asks you what drive you want to install it on, click on options and delete each partition on the drive, leaving just 1 undone partition, dont format it or anything just select after you delete all the partitions and hit next, the setup will handle everything from there.
By doing this we are getting rid of the old file system and master boot record, just in case it is infected and a new one will be made :-)
Shane
-
Ok, thanks for that Shane. Tried a couple of other things I found but still no joy - I can't understand why replacing the registry hive from the day of the repair install hasn't worked - that should be fresh! :confused: Maybe it's not the registry, I've tried a bootsect repair as well but that's made no difference either. Chkdsk is still stuck trying to correct incorrect index entries on my E: drive as well, but I can't get that to complete, and manually deleting the files and folders causing the problem isn't working either as an error box pops up saying the file is corrupt and unreadable so to run chkdsk!!! :teeth: going round in circles...
Unfortunately as I'm in the middle of trying to sort a house move out next week, I don't have a lot of time to mess about trying loads of different fixes, and to do the clean install I'll need to backup everything manually via the dos prompt in RE, so it might have to wait, unless I can squeeze it in before I move.. :undecided:
I've never done a clean install/factory reset before, will the failed chkdsk error/corrupt file/folder/sector cause problems with the install? As you're saying not to format the drive I'm wondering whether this could be an issue. Also if I'm deleting partitions, as well as my E: (data), and OS (D: in RE), there's also a Recovery partition (C: in RE) and a Hidden 14Mb FAT32 partition showing up in diskpart - which of these do I mess with & delete if I get to the install?? I don't want to remove something that I can never get back again and screw it up even more! :wink:
-
When I do a fresh install I do the whole drive, I dont ever keep the store bought machines default partitions as I never use their restore option and I want that space they are taking lol
Shane
-
Ah I see, thanks. If there's an option to keep it I might just do that, bit wary about the whole process to be honest, as I've never done it and don't want to cock it up, but it does look like it needs doing. :undecided:
In the absence of a bootable machine though, and yours over the weekend, and due to exhausting my attempts to get the machine to boot (think the MBR had somehow been screwed up, maybe by the "trojan" or whatever, but nothing I found and tried worked - even fixes marked "this works for everyone"! :cheesy: ) I've decided to restore the system image for now, just so I can have a working machine which I can get a full program list off of and also do a full file check and backup in Windows (rather than more painfully with dos in the RE!).
So I'm now back to my pre-Repair install state, with non-working WU, and just checked MBAM and it's Still found the same trojan in rpcss.dll+ that it found last week, after all the updates etc! :confused: not sure how if the machines been rolled back, and MBAM is the only scanner that picked it up! Even Virustotal says it's clear (0/57, including with Malwarebytes!), and looking online it appears that this file isn't even needed for Windows 7 (the rpcss.dll that is, I can't find any reference online to a .dll+!! :omg:), so I'm wondering if it was maybe a false positive? It's quarantined and gone though (apparently, I had to delete it manually even though MBAM said it had quarantined it...) so hopefully no issues there... :rolleyes:
Anyway I'm going to run all the scans I can to be safe, update as much software as I can (including Windows if it will), then I've got my move to sort out and then a huge backload of work to tackle as well just to try and keep afloat. :sad: It's probably going to be a couple of weeks at least before I get round to getting back here to doing a clean install and the stuff mentioned that's needed before that, so I'm going to mark this as Solved (as it essentially was as far as the updates and missing service package files were concerned before I restored the system image) and then if I have any issues or questions with the install I'll post a new topic at that point.
And before I forget or sign off temporarily (though I'll still be around), many big Thanks again Shane & Boggin and all on here who have helped, greatly appreciate it all :smiley: :artist:
-
My computer is a Dell XPS Studio which came with Vista installed and, eventually, upgrade disks for Windows 7.
I had read these posts and was ready to attach a "Pre-scan Log" which indicated 6,969 files verified and 3,484 files corrupt. I didn't count them. :cheesy: I decided to run FixWU.exe one more time to record the error message that I got on the first run. The error message was 0cx8000247. I did a quick search on this number and found the following link: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/error-code-0xc8000247-cant-install-updates/198166df-9549-e011-8dfc-68b599b31bf5
The answer to this question referred to the need for an update to Intel Rapid Storage Technology Driver (IRRT) and gave the following link: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02219204&lc=en&cc=uk&destPage=document&dlc=en&product=
Upon completion of the IRRT update, I ran FixWU again and it ran successfully. Remember all of the re-starts were performed. I then ran the Pre-scan again and found no errors. I then ran Windows Update successfully.
I hope that this information is helpful.
Bill
-
Thanks wg, that all sounds rather interesting and possibly helpful as well :artist:
I've not seen that WU error message before (surprisingly, as I've seen quite a few others! :cheesy:), but I've definitely had similar issues to the posts in the links you've provided - .NET, updating anything from MS etc - and I have used the FixWU tool several times, but never with any (apparent) success. Not sure if my machine has an IRRT though, but it does have Intel drivers on it, which as far as I'm aware are up to date... :undecided:
Anyway, I'm still in the middle of massive upheaval at the moment and haven't even hooked my Dell up for a couple of days now, but when things calm down and I get some time I'll look into these again on the desktop and see if I can get anywhere with them before I go down the full backup/clean install route.
Cheers :smiley:
-
My computer is a Dell XPS Studio which came with Vista installed and, eventually, upgrade disks for Windows 7.
I had read these posts and was ready to attach a "Pre-scan Log" which indicated 6,969 files verified and 3,484 files corrupt. I didn't count them. :cheesy: I decided to run FixWU.exe one more time to record the error message that I got on the first run. The error message was 0cx8000247. I did a quick search on this number and found the following link: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/error-code-0xc8000247-cant-install-updates/198166df-9549-e011-8dfc-68b599b31bf5
The answer to this question referred to the need for an update to Intel Rapid Storage Technology Driver (IRRT) and gave the following link: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02219204&lc=en&cc=uk&destPage=document&dlc=en&product=
Upon completion of the IRRT update, I ran FixWU again and it ran successfully. Remember all of the re-starts were performed. I then ran the Pre-scan again and found no errors. I then ran Windows Update successfully.
I hope that this information is helpful.
Bill
Now that is a really good find. I wish there was deeper info on it and why the driver would be part of the problem and solution.
Shane