Windows 7 update fails and Windows not genuine message is appearing

[louk1]

Tom,

Should I use the same procedure...with the Windows 7 disc as above?

Louis

 

[tom982]

Hi Louis,

Sorry for being so unclear in my last post! I thought I'd posted instructions, but apparently not.

Download the attached file, louk1_SURT_Fix_v3.reg and save it to your Desktop. Double-click on the file to run it. You will be asked to confirm whether you wish to merge this file to the registry, click Yes. Then reboot, run the SURT, and upload the CheckSUR.persist.log please!

Tom

 

[louk1]

Tom,

Sorry. I am being pulled away for several hours. Will take care of the task when I return.

Louis

 

[tom982]

Louis,

No problem, thanks for letting me know.

Tom

 

[louk1]

Tom,

I have completed the tasks above and the log is attached. I'm sorry that this has been so complicated. Sometimes I feel that Microsoft and their Windows products are somewhat like the television weather forecasters...they can make mistakes a good deal of the time...the forecasters will still get paid and Mr. Gates will continue to make a lot of money.

I have been using MS OS since the mid 1980's and am amazed at how they still have a product that can get so very difficult to deal with.

Thanks again.

Louis

 

[tom982]

Hi Louis,

There isn't a log attached to that post, would you mind uploading it again please?

No need to apologise! It's not your fault at all. The more complicated the problem, the more I learn, so I'm not complaining. My only concern is how much of your time I'm taking up as this problem really isn't playing nicely!

Tom

 

[NoelDP]

I have been using MS OS since the mid 1980's and am amazed at how they still have a product that can get so very difficult to deal with.

Thanks again.

Louis

The problem is that the 'simpler' and more 'user-friendly' the interface, the more has to go on in the background, and the more there is to go wrong.
The average competence of the user-base has dropped as well - from the expert/business user, through the techie hobbyist, to the more highly-educated, and then to the middle-school dropout. The accompanying problems get left longer and become more complex as a result. Machines are used for purposes that were never envisaged 10 years ago, let alone 30 years ago, and the infrastructure is struggling to keep pace with the rate of change, leading to disparities and holes, with resulting potential vulnerabilities, and a definite gap in the learning curve.
The advent of 'devices' like the iPad has killed the idea that you actually need to think about using a computer - and some people who have only ever used such devices would be totally stumped to be faced with a real computer's interface, be it a Mac or a PC. It's for this reason that MS went the two-path route with Windows 8 - RT for the device generation and Win 8/Pro for the PC generation.

... and I'm rambling again It must be bedtime

G'night all.

 

[louk1]

Tom,

It should appear now.

Louis

 

[tom982]

Hi Louis,

Thanks for the log. But unfortunately, there was no changes there either. I'm going to try a different approach which will tell us what's going wrong:

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter afterwards
   
   REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0" /v "Package_4_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2"
   
   
4. When asked to confirm the deletion, please type y and press Enter
   
5. It will then attempt, and hopefully succeed with, the deletion.
6. Right-click anywhere in the command prompt Window and click Select All then press Enter. This will copy the text to your clipboard. Paste this into your next post please. If this fails, then could you upload a screenshot of the window please?

Tom

 

[louk1]

Microsoft Windows [Version 6.1.7601]
Tom,

I opened command prompt with administrator privileges and this is the result.

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd..

C:\Windows>cd..

C:\>REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Com
ponent Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf38
56ad364e35~amd64~~0.0.0.0" /v "Package_4_for_KB2530548~31bf3856ad364e35~amd64~~6
.1.1.2"
Delete the registry value Package_4_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.
2 (Yes/No)? y
ERROR: Access is denied.

C:\>

 

[tom982]

Hi Louis,

Just for future reference, you didn't need either of those cd commands.

Well there we have it, Access is denied. I'm still surprised that it failed from the recovery environment - as far as I know, permissions don't apply from there.

Noel suggested to me that it might be because only TrustedInstaller has write access to these files, so I would like to test that theory.

I would like you to download a tool, devxexec.exe, from this link:

Info: DevelopEx Blog » devxexec
Download Link: http://developex.com/downloads/devxexec.exe

Then copy and paste it into C:\Windows\system32

Then open up a Command Prompt as an Administrator and type this command please:

Do not change the directory before running this one!

devxexec.exe /user:TrustedInstaller cmd

If it gives you a warning, click OK, then a new Command Prompt window should open. Close the one that you have just been using, so that you are left with the blank new one, then run this command please:

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Com
ponent Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf38
56ad364e35~amd64~~0.0.0.0" /v "Package_4_for_KB2530548~31bf3856ad364e35~amd64~~6
.1.1.2"

And copy the output as before please.

Tom

 

[louk1]

Tom,

Here are the results. Thanks to Noel for joining in.

Louis

 

[tom982]

Hi Louis,

I think you've entered the command incorrectly. Just to clarify, this is one command that spans across four lines, not four commands Could you select all of the bold text below, then copy and paste this into the TrustedInstaller command prompt window (instructions in last post) and press enter:

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Com
ponent Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf38
56ad364e35~amd64~~0.0.0.0" /v "Package_4_for_KB2530548~31bf3856ad364e35~amd64~~6
.1.1.2"

Tom

 

[NoelDP]

I get an error message running the initial setup command.

---------------------------
Error
---------------------------
Error 2 (Run SetPermission Process). The system cannot find the file specified.

CommandLine: devxexec.exe /user:TrustedInstaller cmd
---------------------------
OK
---------------------------

 

[tom982]

I get an error message running the initial setup command.

---------------------------
Error
---------------------------
Error 2 (Run SetPermission Process). The system cannot find the file specified.

CommandLine: devxexec.exe /user:TrustedInstaller cmd
---------------------------
OK
---------------------------

Press OK, then have a look in Task Manager. You should still see a cmd instance run under TrustedInstaller

 

[louk1]

Tom,

I received the same message that Noel posted above.

 

[louk1]

Tom,

I do not see TrustedInstaller in the task manager after clicking OK to the error.

 

[NoelDP]

Yep - the new window is running as WMI... they need to do something about that message!

 

[louk1]

Tom,

The command prompt line is C:\Windows\System32\cmd.exe

 

[louk1]

Tom,

I just tried the four lines again...copy and pasted into the second command prompt and received the same result as before. Sorry.

Louis