[SOLVED] Windows 7 PRO SP1 64-Bit Multiple Windows Update Failures from Dec 2018 On

When you right-click on a a folder or file with the File Explorer on my system, there is no Send To...Compressed (zipped) folder option, to wit:

44387

I have to manually create ZIP files; I use a product called Bitzipper which has very aggressive ZIP compression. It has super-zip compression that produces zipx files, and also handles Unix/Linux tar files. (BTW: I met the creator of the ZIP process - Phil Katz - at Bell Labs. He got totally screwed by the software pirates. Unfortunately Phil died over 10 years ago.)

If I can't directly upload the COMPONENTS.ZIP file I'm going to build, I will place it my dropbox and post a URL link to it.
 
OK, Bitzipper will not insert a file without an extension into a ZIP file. So I made a copy of the C:\Windows\System32\Config\components (as it’s actually named on my system – lower case) into harmless user space, renamed it components.xxx there and loaded it into the newly created 02-27 COMPONENTS.zip file. So when you extract components.xxx from the ZIP file, you can rename it to drop the file extension if you wish.

It was indeed too big to upload directly into forum thread message so I put it into my dropbox. Here is a URL link to the ZIP file in my cloud dropbox: https://www.dropbox.com/s/j34ww5zyswap0cp/02-27 COMPONENTS.zip?dl=0. Please let me know when you have copied it to your file space so I can deleted it from my dropbox; I’m close to the Dropbox “freebie” limit and I use Dropbox to distribute my music.
 
Strange. It appears for me.
Click to expand...

Well, the Send To menu has contextual contents. For example, if I right click on a program in the Start->All Programs list, I will get an opportunity to send the selection (usually an icon) to the Desktop. You didn’t see that in the screen shot I sent you because I was operating on a file in the My Files folder instead.

Here are two possible explanations in descending order of likelyhood:
  • You’re running a Windows version later than 7.

    What you see could be an enhancement in Windows 8, 8.1 or 10. (I doubt there will be an official Windows version release later than 10. They will just keeping adding to the bloat without redesignating it.)

  • You have installed a ZIPping app that added the Compressed File option to the file context Send To menu.

    In the screen shot I sent you will see a Dropbox option in the Send To menu. That first appeared when I installed Dropbox.
 
Further research makes me believe that my initial Send To menu conjecture is correct, and that the Microsoft Office change came probably with Service Pack 1 for Windows 7. That is because both the users on this system that have E:\Users as their User Profile base (including the one I run on) were created on Windows 7 before SP1 was issued, directly after I bought this custom box.

I created a C Drive Only user much later (well after SP1 was installed) only to facilitate the copy of the Windows partition on my old SSD, because my disk controller can handle only two internal drives. I had to temporarily mount the new SSD in the place of my E: HRD in order to run the Samsung Disk Migration tool. Once the migration was complete I removed the old SSD, remounted the new SSD in that place and remounted the HRD back in its original place. (Mounting order in the cage is important because of the cabling to the disk controller. The boot drive must be nearest the controller in the cage.)

I logged onto the C Drive Only user just for giggles and what do you know: the Sent To menu behaves exactly as you describe, while on both the E: users, it behaves as I documented in last night’s final screen shot. The Send To menu for any user I create from now on will behave as you described, while the two "old" user accounts will always behave as I described.

Mystery solved.

BTW: there is a neat Registry hack I found (a regedit script) to facilitate the creation of off-Windows-parition users which was installed to create those two "old" users; I wrote another regedit script to restore the New User Profile registry data before recently creating the C Drive Only user account.
 
Thank you for the additional information.

Please do the following:

Install Update with DISM

  1. Download this update and save to your desktop. The file name will be IE11-Windows6.1-KB2957689-x64.cab.zip.
  2. Right-click on this file and select Extract All... Click the Extract button. You can close the folder window that opens
  3. Click on the Start button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator. Go ahead and allow if you receive the UAC prompt.
  5. Copy and paste the following command into the command prompt window and press enter.

    dism /online /add-package /packagepath:%userprofile%\desktop\IE11-Windows6.1-KB2957689-x64.cab
  6. You should receive the message:
    The operation completed successfully.
    Restart Windows to complete this operation. <---You may not get this line.
    Do you want to restart the computer now (Y/N)? <---You may not get this line.

Go ahead and do so if prompted. Let me know what errors if any come up. If you do get errors, please zip/attach your CBS.log
 
OK, will do. On my computer userID the unzipping will have to be a bit different, but what you want is something I've done many times before. Basically yoiu want me to attach the dism executable(s) to my desktop, unzip IE11-Windows6.1-KB2957689-x64.cab onto my desktop as well, and then execute the dism command you wrote in a CMD window. I do this sort of thing all the time and will probable open a CMD window ahead of time and execute the command in it, to save the return. This will have to be later on tonight, sorry for the delay. And thanks again for your continuing help.
 
I ran the procedure, it ran without errors and did not request a reboot (so I did not), to wit, from the Administrator: cmd Shortcut screen.

========================================================
E:\Users\Dick\My Files>dism /online /add-package /packagepath:%userprofile%\desk
top\IE11-Windows6.1-KB2957689-x64.cab

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.18489

Processing 1 of 1 - Adding package Package_for_KB2957689~31bf3856ad364e35~amd64~
~11.2.1.0
[==========================100.0%==========================]
The operation completed successfully.

E:\Users\Dick\My Files>
==========================================================

The CBS Log file ZIP is attached.
 

Attachments

softwaremaniac said:
You will have to do this for many updates as there are many keys missing. :)
Click to expand...

Given that you already know the constituency of the “many keys missing” and thus can prepare a number of the cab ZIP files in advance on your Mega.nz cloud space, i.e., you don’t have to look at the CBS.log results of each Deployment Image Servicing and Management tool run and a CheckSUR.log before deciding how to compose the next cab file for dism, I think I know a way we can speed up this process.

Decide how many dism runs I can do before you need to see a CheckSUR.log, and prepare that many cab.zip files. Post that many cab.zip files on your cloud space and put all the URLs in sequence in your next thread message. I will run each of the corresponding dism runs in sequence, and for each place the CMD Window sysout and dedicated CBS.log in a unique numbered ZIP file. After the chosen dism run quantum is complete I will do the SURT run and place the resulting CheckSUR.log in another ZIP file. Let’s say you believe I can do five dism runs before you need a SURT run to check on progress. I will make the five dism sysout – CBS.log numbered ZIP files and the additional CheckSUR.log ZIP file and post all six ZIP files in my answering thread message. In this example, we will have cut the number of thread interaction cycles to do five runs by close to 80%, which IMO would save a lot of time.

Of course it’s up to you how we actually proceed, so if you don’t like this idea, so be it.
 
OK, Man, Thanks a lot. It's too late to tackle this tonight but I will get on it tomorrow morning.
 
I processed these dism run cab.zips in the order you listed them in your last message, and included the dism run sysout image for each along with a fresh CBS.Log file in each of the “DISM <run number>” uploaded ZIP files.. The first two “IE” cabs runs ran without requiring a reboot. The 3rd run - the first of two “Windows…” cab runs ran and required a reboot, and the pre-full-Windows-OS-startup “Preparing to configure Windows” phase completed successfully: an apparently successful Windows update. However, the 4th run for Windows6.1-KB4471318-x64.cab.zip - also requiring a reboot failed in the pre-full-Windows-OS-startup “Preparing to configure Windows” phase, requiring a second reboot to revert back to the system state before that Windows update was attempted. (All reboot requests were honored after I captured the CMD window sysout images.) After the four runs I reran SURT and uploaded a ZIP of a fresh CheckDUR.Log.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top