Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - nelsongeli

Pages: [1]
1
General Computer Support / Re: Manually replacing Package files on Windows 7 x64
« on: May 15, 2015, 07:31:53 am »
Well, I finally gave up and did a reinstall of Windows 7.  The computer was continuing to deteriorate and lose functionality.  I think there was more wrong than just the updater.  It blocked me at every turn and given the time involved, it appeared easier to reinstall windows and replace the programs.  I do have a good backup, so it shouldn't take too long.

Thanks for your help.  I will be back if I have any new problems, before they get out of hand.  I need to make this one as solved, but I can't seem to find the right button to click. 

2
General Computer Support / Re: Manually replacing Package files on Windows 7 x64
« on: May 13, 2015, 09:21:52 am »
Your program to take control of the file folder worked great.  The only problem now is when I open the command prompt to do an sfc scan, there is no option to run as administrator.  The take ownership option appears but when used the command prompt disappears.

I loaded the files from my Windows 7 Ultimate laptop with no problem.  Unfortunately they did not change anything.  All the same files still show up in the pre scan and the windows updater and sfc scan tools still do not work.

Tweaking.com - Windows Repair - Pre-Scan
Computer: GENE-VM (Windows 7 Ultimate 6.1.7601 Service Pack 1) (64-bit)
Started at (5/13/2015 12:19:54 PM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (5/13/2015 12:19:54 PM)

These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 24)
C:\Windows\servicing\Packages\Package_149_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_150_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_151_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_152_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_153_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_154_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_155_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_156_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_157_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_158_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_159_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_160_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_161_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_162_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_163_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_164_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_165_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_166_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_167_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_168_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_169_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_170_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum

I went to the download site you recommended to get the KB files.  When I download the file for KB2756882 I get one file name that looks like this -  AMD64-all-windows6.1-kb2756882-x64_0c9661a559c64b8f1b9728f5b3daa18828895831.msu.  On my computer I have multiple files with different names ranging from Package-149_KB2756882* to Package-170_KB275682.  I must be doing something wrong!

3
General Computer Support / Re: Manually replacing Package files on Windows 7 x64
« on: May 12, 2015, 09:29:50 pm »
I want to mention that I have a laptop with Windows 7 x64 Ultimate that is working well.  Could I get the files I need by copying them from that computer?  When I do get the correct files, I am going to have a problem putting them in the correct folder on the desktop.  I tried installing one of these files from my laptop and ended up spending 4 hours fighting with security and ownership of the folder.  I could not get permission to change the files.  I have given up for tonight.

Here is a copy of the scan from my desktop with the problems.  It lists all the bad package files.

 Tweaking.com - Windows Repair - Pre-Scan
Computer: GENE-VM (Windows 7 Ultimate 6.1.7601 Service Pack 1) (64-bit)
Started at (5/13/2015 12:18:35 AM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (5/13/2015 12:18:35 AM)

These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 26)
C:\Windows\servicing\Packages\Package_149_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_150_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_151_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_152_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_153_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_154_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_155_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_156_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_157_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_158_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_159_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_160_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_161_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_162_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_163_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_164_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_165_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_166_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_167_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_168_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_169_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_170_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_171_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_172_for_KB2756822~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB2991963_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum

Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
These files do not keep the repairs from working, you may still run the repairs in the program.

If you need help in replacing these files, post on the Forums at Tweaking.com for help.

Files Checked & Verified: 5,421

Done (5/13/2015 12:18:51 AM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (5/13/2015 12:18:51 AM)

No problems were found with the Reparse Points.

Files & Folders Searched: 288,753
Reparse Points Found: 96

Done (5/13/2015 12:19:12 AM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (5/13/2015 12:19:12 AM)

No problems were found with the Environment Variables.

Done (5/13/2015 12:19:12 AM)
--------------------------------------------------------------------------------

Done (5/13/2015 12:19:12 AM)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Done (5/13/2015 12:19:12 AM)
Scan Complete - Problems Found!

You can use the Repair Reparse Points or Repair Environment Variables tools at the bottom of this Window if needed.

While problems have been found, you can still run the repairs in the program.
But for the best results it is recommended to fix the problems reported in this scan if possible.
If you need help fixing any of the items in the log, just post in the forums at Tweaking.com for help.


4
General Computer Support / Manually replacing Package files on Windows 7 x64 - SOLVED
« on: May 12, 2015, 11:54:23 am »
I am having a problem with Windows 7 Ultimate x64 updates and the SFC scan tool.  The windows update screen shows an error code 80073712.  The sfc /scan tool will not run even in safe mode.  It always shows "resource protection could not perform the requested operation". 

I ran the Tweaking step 1 pre scan tool and it indicates I have bad package files related to KB2756822.  It indicates that I should manually update these files.  I have attached a copy of the scan results with the information.  I tried to update these files by doing a search for KB2756822, but the only download I could find and run indicated that it wasn't for this computer.  It may not have been the correct Windows 7 x64 version.  I was thinking about upgrading to the Tweaking Pro level repair tool, but I doubt that it would help solve my problem.  Is there a way to update these corrupted package files, or am I going to have to reload Windows 7?

Pages: [1]