Main Forum > General Computer Support

Missing Windows Servicing Packages files & update problems

<< < (11/33) > >>

Boggin:
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.

Tone111:
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?

Boggin:
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 -

Tone111:
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...

Boggin:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page