[mini-rant] Microshaft screwed up again[mini-rant]

flhrci

flhrci

Final Approach
Joined
Jan 26, 2007
Messages
5,932
Location
Groveport, OH
Display Name
David
January security roll-up of 142.8 MB downloaded today by my Win 7 machine. It has tried to install several times and fails each time with no explanation. Grrrrr...

Win 10 had one a couple months ago that did the same thing. I sure wish they would get their act together before these updates get released.

Sorry this is not a Sac Arrow quality rant btw.

David
 
AggieMike88 said:
We did notice the distinct lack of lettuce wrapped burgers, bicycle short wrapped manly parts, and fast food uniform wrapped females of Asian descent.
Click to expand...
I'll have to work on all that. But this ain't California. That's all I can say.
 
There is a Windows update log that documents what's failing and why

Sent from my SM-G935V using Tapatalk
 
January, 2017 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3212646)

Installation date: ‎1/‎11/‎2017 1:59 PM

Installation status: Failed

Error details: Code 80073701

Update type: Important

A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

More information:
http://support.microsoft.com/kb/3212646

Help and Support:
http://support.microsoft.com
 
flhrci said:
January, 2017 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3212646)

Installation date: ‎1/‎11/‎2017 1:59 PM

Installation status: Failed

Error details: Code 80073701

Update type: Important

A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

More information:
http://support.microsoft.com/kb/3212646

Help and Support:
http://support.microsoft.com
Click to expand...
That's not from the update log . It's a .log file that has every step saying what the update is doing while trying to install

Sent from my SM-G935V using Tapatalk
 
WannFly said:
https://support.microsoft.com/en-us/kb/902093

Sent from my SM-G935V using Tapatalk
Click to expand...
Did not know about that one. Thanks. Still no help though, at least to a non-IT person.


2017-01-11 18:55:11:937 892 528 AU ## START ## AU: Search for updates
2017-01-11 18:55:11:937 892 528 AU #########
2017-01-11 18:55:11:939 892 528 AU <<## SUBMITTED ## AU: Search for updates [CallId = {C25CCA9A-71C7-4746-A3D5-6FE574D12F09}]
2017-01-11 18:55:11:939 892 2658 Agent *************
2017-01-11 18:55:11:939 892 2658 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2017-01-11 18:55:11:939 892 2658 Agent *********
2017-01-11 18:55:11:939 892 2658 Agent * Online = No; Ignore download priority = No
2017-01-11 18:55:11:939 892 2658 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2017-01-11 18:55:11:939 892 2658 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2017-01-11 18:55:11:939 892 2658 Agent * Search Scope = {Machine}
2017-01-11 18:55:19:529 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:19:536 892 2658 Agent WARNING: Failed to evaluate Installed rule, updateId = {850138F2-E1D3-4E29-B962-7324C1C6AE1D}.202, hr = 80070490
2017-01-11 18:55:19:694 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:19:702 892 2658 Agent WARNING: Failed to evaluate Installable rule, updateId = {850138F2-E1D3-4E29-B962-7324C1C6AE1D}.202, hr = 80070490
2017-01-11 18:55:19:860 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:29:343 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:29:344 892 2658 Agent WARNING: Failed to evaluate Installed rule, updateId = {CC5D5D63-32BB-4593-BD6F-3B61BA97707F}.204, hr = 80070490
2017-01-11 18:55:29:363 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:29:364 892 2658 Agent WARNING: Failed to evaluate Installable rule, updateId = {CC5D5D63-32BB-4593-BD6F-3B61BA97707F}.204, hr = 80070490
2017-01-11 18:55:29:383 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:32:278 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:32:280 892 2658 Agent WARNING: Failed to evaluate Installed rule, updateId = {F9164872-3E27-4410-B4FC-038814549BB1}.105, hr = 80070490
2017-01-11 18:55:32:505 892 2658 Handler FATAL: UH: 0x80070490: EvaluateApplicability failed in CCbs::EvaluateApplicability
2017-01-11 18:55:36:198 892 2658 Agent * Added update {C2D37DE8-9638-468D-9575-5764F0D086D1}.200 to search result
2017-01-11 18:55:36:198 892 2658 Agent * Added update {7071D98C-3EA8-47DD-871E-8BC19EA05FF4}.200 to search result
2017-01-11 18:55:36:198 892 2658 Agent * Found 2 updates and 86 categories in search; evaluated appl. rules of 2960 out of 6342 deployed entities
2017-01-11 18:55:36:200 892 2658 Agent *********
2017-01-11 18:55:36:200 892 2658 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
 
Tried your suggestion. A few things got fixed but the same update still fails. I am just going to turn off Windows update for awhile I think.
Capture5.PNG
 
My first PC ran DOS 6.0 & Win 3.1 and I felt like a late comer to the PC age. Still even then people were bashing MS. All these years later, people are still bashing and they are still in business and making tons of money. It is rather funny in a way.
 
SkyDog58 said:
My first PC ran DOS 6.0 & Win 3.1 and I felt like a late comer to the PC age. Still even then people were bashing MS. All these years later, people are still bashing and they are still in business and making tons of money. It is rather funny in a way.
Click to expand...
We're all human. Bashing others is in our blood.
 
flhrci said:
I sure wish they would get their act together before these updates get released.
Click to expand...
I wonder if MicroSh*t adopted crApple's release policy: get the code monkeys to produce something good enough and let the general public test it. If it's bad, they'll report it. Free testing environment, yay! :)
To be fair, Stoogle employs the same system. I think they all just started doing it to cut down cost and maximize profits.
 
BigBadLou said:
I wonder if MicroSh*t adopted crApple's release policy: get the code monkeys to produce something good enough and let the general public test it. If it's bad, they'll report it. Free testing environment, yay! :)
To be fair, Stoogle employs the same system. I think they all just started doing it to cut down cost and maximize profits.
Click to expand...

Software makers have been doing that long before either Microsoft or Apple existed.

"Software Engineering: When it doesn't even need to be good enough to do the job, to ship it!"
 
You must log in or register to reply here.
Back
Top