On Thu, 19 Aug 2021 17:33:54 -0400, Paul <nospam@needed.invalid> wrote
as underneath :

snip
>
>But it's a damn nuisance to send a thing like that to
>another person, as it might take a rather large dual layer
>DVD to do it, or a USB stick, and sending it by mail. If
>you "collect" at your end, your upload rate on the Internet
>service is going to throttle how fast you can get it
>to the remote "target" storage folder.
>
>BTW - Did using Firefox on the target machine and doing the
> ssllabs command on "walmart.com" indicate anything interesting ?
> Paul
Agreed! Size of last shout fully loaded WSUS file for Windows 7:
WSUS v11'8'3 LAST W7 inc Office2010,13,16 x32'x64' 15-01-2020 - 22'6GB
The last shout file for XP was even bigger, I think about 29 GB! C+

On Thu, 19 Aug 2021 17:33:54 -0400, Paul <nospam@needed.invalid>
wrote:

>jetjock wrote:
>> On Wed, 18 Aug 2021 21:15:03 -0500, jetjock <jetjock@unkown.com>
>> wrote:
>>
>>> On Wed, 18 Aug 2021 19:42:24 -0400, Paul <nospam@needed.invalid>
>>> wrote:
>>>
>>>> jetjock wrote:
>>>>> On Wed, 18 Aug 2021 15:07:31 -0400, Paul <nospam@needed.invalid>
>>>>> wrote:
>>>>>> https://support.microsoft.com/en-us/topic/support-for-urgent-trusted-root-updates-for-windows-root-certificate-program-in-windows-a4ac4d6c-7c62-3b6e-dfd2-377982bf3ea5
>>>>>>
>>>>>> Win7 x86 http://www.microsoft.com/download/details.aspx?familyid=a588e9e4-f1b4-4c4d-991b-d423da4c9f7d
>>>>>>
>>>>>> Win7 x64 http://www.microsoft.com/download/details.aspx?familyid=d3f212e9-2c49-4cd6-bd2f-51cf8a712ba6
>>>>> Should I use the above x64 link to do the Windows updates?
>>>>> See my above question please. I really do appreciate all the info you
>>>>> provide, but since my knowledge is miniscule compared to yours, I can
>>>>> really get lost deciphering it all sometimes! :-) My best guess as
>>>>> to what I should do for him tomorrow is try Windows Update first. If
>>>>> that doesn't fix the problem, try Win7 x64
>>>>> http://www.microsoft.com/download/details.aspx?familyid=d3f212e9-2c49-4cd6-bd2f-51cf8a712ba6,
>>>>> and if none of that works, try the WSUSoffline. Am I close? Hate to
>>>>> keep bugging you but preventing mistakes is much easier than
>>>>> correcting them!
>>>>>
>>>>> >>>>>>>>>>jetjock<<<<<<<<<<
>>>> The Win x64 one is for your 64-bit OS.
>>>>
>>>> At a minimum, it increases the frequency of automatic
>>>> checks for certificates to a once-a-day check.
>>>>
>>>> And at this point, we don't know if the certificate subsystem
>>>> is fully healthy, and like you, certificates are a mystery to me.
>>>>
>>>> I would install that update, just so it's well equipped for
>>>> handling certificates.
>>>>
>>>> *******
>>> Ok, so it looks like run the Microsoft Win x64 first.
>>>> The WsusOffline has the links to the Microsoft certificate files.
>>>> The funny part being, the files stop at 2018 or so.
>>>> And that's the static list of items, WsusOffline wants to install.
>>>> The list does not seem to be dynamically generated from a
>>>> master list - like all good things the WsusOffline team does,
>>>> they assemble some of those lists from disparate sources.
>>>> For example, their detection of what it takes to tip Vista upright,
>>>> is first-class.
>>>>
>>>> Version 11.8 of WsusOffline, the Legacy OS tab, might be the
>>>> last version of WsusOffline supporting Windows 7.
>>>>
>>>> If your Windows 7 in system control panel says that SP1 is
>>>> already installed "Win 7 SP1", then you don't need to include
>>>> that tick box in a Wsusoffline collection run. And you only
>>>> absolutely need to select the x64 option, if working on a
>>>> x64 setup. Those can help reduce the collection time.
>>>>
>>>> *******
>>> If that doesn't work, then run WUSAOffline. If that doesn't work, I
>>> just won't pay your bill! :-)
>>>> You can use the "to test a website line" from the following re-post.
>>>> Now, I don't know if any of the website certificates are checked
>>>> against the chain of trust on the machine or not. The web browser
>>>> certificates might be used for that. But your browser was just
>>>> installed...
>>>>
>>>> To test a website:
>>>>
>>>> https://www.ssllabs.com/ssltest/analyze.html?d=walmart.com <===
>>>>
>>>> To determine the feature set of the browser:
>>>>
>>>> https://www.ssllabs.com/ssltest/viewMyClient.html
>>>>
>>>> This is an example of a browser armed for mid-sized bears.
>>>>
>>>> Protocols [of my client browser]
>>>> TLS 1.3 No <=== web sites using *only* this, are a problem
>>>> TLS 1.2 Yes
>>>> TLS 1.1 Yes
>>>> TLS 1.0 Yes
>>>> SSL 3 No \___ User should disable these in the browser, and
>>>> SSL 2 No / browser may have done this at the source end already
>>>>
>>>> Cipher Suites (in order of preference)
>>>>
>>>> TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) Forward Secrecy 256
>>>> OLD_TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcc13) Forward Secrecy 256
>>>> TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Forward Secrecy 128
>>>>
>>>> Still, I don't know of too many "consumer-oriented utilities"
>>>> in this domain. Lots of chuckleheads to "help you check *OUR* certificate is there".
>>>> But nobody interested in vetting the entire store for correctness.
>>>> I don't know how to do that. I rely on the above two web pages,
>>>> to provide hints, such as they are.
>>> Will do, and again, many thanks!
>>
>> Houston, we have a problem!! :-)
>>
>> First of all I tried just running Windows Update from his computer
>> and got an error message (see the third photo). I checked the update
>> history and saw that one update had been successfully installed (see
>> second photo). I then ran the WSUSoffline updater and it failed the
>> verification check (see first photo).
>> https://www.sendspace.com/filegroup/1a%2BuZPuNWXgcmTOjM1kJtdm39qYjXblk.
>>
>> I then ran the
>> http://www.microsoft.com/download/details.aspx?familyid=d3f212e9-2c49-4cd6-bd2f-51cf8a712ba6
>> for x64 and it installed KB 3004394. If Windows will not update on
>> it's own though, enabling it to check for updates more often isn't
>> going to help much I don't think.
>>
>> I don't know what I would have done if WSUSoffline had passed
>> verification as I have absolutely no clue as to where it downloaded
>> the updates to. Can you give me a hint please? Then, if I found
>> them, does it tell me how to install them? Or, is it obvious by the
>> file extension?
>>
>> It appears that something is seriously messed up in Windows if it
>> won't even do it's own updates. I clicked on "Get help with this
>> error" on the Windows Update page, but all I got was help for a bunch
>> of other errors. Maybe you'll have better luck deciphering it than I
>> did.
>>
>> Speaking of luck, the Intel Graphics driver did the trick to enable
>> "Sleep" mode for him. So, at least something worked!
>>
>> Any more suggestions will be gratefully accepted.
>
>Logically, the target machine has a certificate problem.
>Windows Updates needs a certificate.
>WSUSOffline needs to be able to do SHA2.
>
>This means that preparatory steps may have to be done
>on a "healthy" machine.
>
>*******
>
>WSUSOffline has some tick boxes to "prepare media", but
>we'll ignore those for the moment.
>
> WSUSOffline folder
> client folder
> preparatory materials
> downloader materials
>
>The downloads are accumulated in the WSUSOffline folder.
>The WSUSOffline folder will grow in size, to as much as
>8GB if you tick too many boxes. It doesn't take much
>"excess" to overdo it.
>
>The "Download" button is relatively small, gray, and near the top
>on Pastebin. This directory listing is 128KB or so long. A text file.
>
>This is a "dir /S" listing of the folder I've got here. I could
>probably cut it down to 4GB without too much trouble. The contents
>are already compressed by Microsoft, so 7ZIP would not perform
>miracles on the content.
>
>https://pastebin.com/XHqXVfh4

What am I supposed to do with the Pastebin.com info? If I download
from that page, what do I do with all that? It appears to me to a
copy of what you have downloaded using WSUSOffline. Correct?
>
>UpdateGenerator.exe is what collects the downloads (the GUI).
>client\UpdateInstaller.exe is what installs at the target machine
>
>You run UpdateGenerator on the healthy technician machine
>and build a "kit".
>
>The "kit" is sent to the recipient, and they run UpdateInstaller.exe
>on the order of five times. There is a reboot after each
>partial install. The early stages ensure the support structure
>is there for things to work. The last step loads in 150 or so
>Windows Updates, one after another.
>
>*******
Are you saying that I can run UpdateGenerator on my machine, and
somehow send BIL the downloaded files? 8GB would take all day (
longer) to "File Transfer" via Team Viewer. Or, could send them on a
USB stick. Would he then just run UpdateInstaller and point it to the
USB drive?
>
>The bare minimum you could do, is to use the chunk of code that
>installs certificates and revokes, and give it a folder to work on.
>
>"DoUpdate.cmd" 78KB script, there is this chunk...
>
> rem *** Install Trusted Root Certificates and Certificate revocation lists ***
> if "%UPDATE_RCERTS%" NEQ "/updatercerts" goto SkipTRCertsInst
> echo Installing Trusted Root Certificates...
> for /F "tokens=*" %%i in ('dir /B ..\win\glb\*.crt') do (
> if exist %SystemRoot%\Sysnative\certutil.exe (
> %SystemRoot%\Sysnative\certutil.exe -f -addstore Root "..\win\glb\%%i"
> ) else (
> %SystemRoot%\System32\certutil.exe -f -addstore Root "..\win\glb\%%i"
> )
> call :Log "Info: Installed ..\win\glb\%%i"
> )
> echo Installing Certificate revocation lists...
> for /F "tokens=*" %%i in ('dir /B ..\win\glb\*.crl') do (
> if exist %SystemRoot%\Sysnative\certutil.exe (
> %SystemRoot%\Sysnative\certutil.exe -f -addstore Root "..\win\glb\%%i"
> ) else (
> %SystemRoot%\System32\certutil.exe -f -addstore Root "..\win\glb\%%i"
> )
> call :Log "Info: Installed ..\win\glb\%%i"
> )
> :SkipTRCertsInst

On Fri, 20 Aug 2021 11:47:08 -0500, jetjock <jetjock@unkown.com>
wrote:

>On Thu, 19 Aug 2021 17:33:54 -0400, Paul <nospam@needed.invalid>
>wrote:
>
>>jetjock wrote:
>>> On Wed, 18 Aug 2021 21:15:03 -0500, jetjock <jetjock@unkown.com>
>>> wrote:
>>>
>>>> On Wed, 18 Aug 2021 19:42:24 -0400, Paul <nospam@needed.invalid>
>>>> wrote:
>>>>
>>>>> jetjock wrote:
>>>>>> On Wed, 18 Aug 2021 15:07:31 -0400, Paul <nospam@needed.invalid>
>>>>>> wrote:
>>>>>>> https://support.microsoft.com/en-us/topic/support-for-urgent-trusted-root-updates-for-windows-root-certificate-program-in-windows-a4ac4d6c-7c62-3b6e-dfd2-377982bf3ea5
>>>>>>>
>>>>>>> Win7 x86 http://www.microsoft.com/download/details.aspx?familyid=a588e9e4-f1b4-4c4d-991b-d423da4c9f7d
>>>>>>>
>>>>>>> Win7 x64 http://www.microsoft.com/download/details.aspx?familyid=d3f212e9-2c49-4cd6-bd2f-51cf8a712ba6
>>>>>> Should I use the above x64 link to do the Windows updates?
>>>>>> See my above question please. I really do appreciate all the info you
>>>>>> provide, but since my knowledge is miniscule compared to yours, I can
>>>>>> really get lost deciphering it all sometimes! :-) My best guess as
>>>>>> to what I should do for him tomorrow is try Windows Update first. If
>>>>>> that doesn't fix the problem, try Win7 x64
>>>>>> http://www.microsoft.com/download/details.aspx?familyid=d3f212e9-2c49-4cd6-bd2f-51cf8a712ba6,
>>>>>> and if none of that works, try the WSUSoffline. Am I close? Hate to
>>>>>> keep bugging you but preventing mistakes is much easier than
>>>>>> correcting them!
>>>>>>
>>>>>> >>>>>>>>>>jetjock<<<<<<<<<<
>>>>> The Win x64 one is for your 64-bit OS.
>>>>>
>>>>> At a minimum, it increases the frequency of automatic
>>>>> checks for certificates to a once-a-day check.
>>>>>
>>>>> And at this point, we don't know if the certificate subsystem
>>>>> is fully healthy, and like you, certificates are a mystery to me.
>>>>>
>>>>> I would install that update, just so it's well equipped for
>>>>> handling certificates.
>>>>>
>>>>> *******
>>>> Ok, so it looks like run the Microsoft Win x64 first.
>>>>> The WsusOffline has the links to the Microsoft certificate files.
>>>>> The funny part being, the files stop at 2018 or so.
>>>>> And that's the static list of items, WsusOffline wants to install.
>>>>> The list does not seem to be dynamically generated from a
>>>>> master list - like all good things the WsusOffline team does,
>>>>> they assemble some of those lists from disparate sources.
>>>>> For example, their detection of what it takes to tip Vista upright,
>>>>> is first-class.
>>>>>
>>>>> Version 11.8 of WsusOffline, the Legacy OS tab, might be the
>>>>> last version of WsusOffline supporting Windows 7.
>>>>>
>>>>> If your Windows 7 in system control panel says that SP1 is
>>>>> already installed "Win 7 SP1", then you don't need to include
>>>>> that tick box in a Wsusoffline collection run. And you only
>>>>> absolutely need to select the x64 option, if working on a
>>>>> x64 setup. Those can help reduce the collection time.
>>>>>
>>>>> *******
>>>> If that doesn't work, then run WUSAOffline. If that doesn't work, I
>>>> just won't pay your bill! :-)
>>>>> You can use the "to test a website line" from the following re-post.
>>>>> Now, I don't know if any of the website certificates are checked
>>>>> against the chain of trust on the machine or not. The web browser
>>>>> certificates might be used for that. But your browser was just
>>>>> installed...
>>>>>
>>>>> To test a website:
>>>>>
>>>>> https://www.ssllabs.com/ssltest/analyze.html?d=walmart.com <===
>>>>>
>>>>> To determine the feature set of the browser:
>>>>>
>>>>> https://www.ssllabs.com/ssltest/viewMyClient.html
>>>>>
>>>>> This is an example of a browser armed for mid-sized bears.
>>>>>
>>>>> Protocols [of my client browser]
>>>>> TLS 1.3 No <=== web sites using *only* this, are a problem
>>>>> TLS 1.2 Yes
>>>>> TLS 1.1 Yes
>>>>> TLS 1.0 Yes
>>>>> SSL 3 No \___ User should disable these in the browser, and
>>>>> SSL 2 No / browser may have done this at the source end already
>>>>>
>>>>> Cipher Suites (in order of preference)
>>>>>
>>>>> TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) Forward Secrecy 256
>>>>> OLD_TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcc13) Forward Secrecy 256
>>>>> TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Forward Secrecy 128
>>>>>
>>>>> Still, I don't know of too many "consumer-oriented utilities"
>>>>> in this domain. Lots of chuckleheads to "help you check *OUR* certificate is there".
>>>>> But nobody interested in vetting the entire store for correctness.
>>>>> I don't know how to do that. I rely on the above two web pages,
>>>>> to provide hints, such as they are.
>>>> Will do, and again, many thanks!
>>>
>>> Houston, we have a problem!! :-)
>>>
>>> First of all I tried just running Windows Update from his computer
>>> and got an error message (see the third photo). I checked the update
>>> history and saw that one update had been successfully installed (see
>>> second photo). I then ran the WSUSoffline updater and it failed the
>>> verification check (see first photo).
>>> https://www.sendspace.com/filegroup/1a%2BuZPuNWXgcmTOjM1kJtdm39qYjXblk.
>>>
>>> I then ran the
>>> http://www.microsoft.com/download/details.aspx?familyid=d3f212e9-2c49-4cd6-bd2f-51cf8a712ba6
>>> for x64 and it installed KB 3004394. If Windows will not update on
>>> it's own though, enabling it to check for updates more often isn't
>>> going to help much I don't think.
>>>
>>> I don't know what I would have done if WSUSoffline had passed
>>> verification as I have absolutely no clue as to where it downloaded
>>> the updates to. Can you give me a hint please? Then, if I found
>>> them, does it tell me how to install them? Or, is it obvious by the
>>> file extension?
>>>
>>> It appears that something is seriously messed up in Windows if it
>>> won't even do it's own updates. I clicked on "Get help with this
>>> error" on the Windows Update page, but all I got was help for a bunch
>>> of other errors. Maybe you'll have better luck deciphering it than I
>>> did.
>>>
>>> Speaking of luck, the Intel Graphics driver did the trick to enable
>>> "Sleep" mode for him. So, at least something worked!
>>>
>>> Any more suggestions will be gratefully accepted.
>>
>>Logically, the target machine has a certificate problem.
>>Windows Updates needs a certificate.
>>WSUSOffline needs to be able to do SHA2.
>>
>>This means that preparatory steps may have to be done
>>on a "healthy" machine.
>>
>>*******
>>
>>WSUSOffline has some tick boxes to "prepare media", but
>>we'll ignore those for the moment.
>>
>> WSUSOffline folder
>> client folder
>> preparatory materials
>> downloader materials
>>
>>The downloads are accumulated in the WSUSOffline folder.
>>The WSUSOffline folder will grow in size, to as much as
>>8GB if you tick too many boxes. It doesn't take much
>>"excess" to overdo it.
>>
>>The "Download" button is relatively small, gray, and near the top
>>on Pastebin. This directory listing is 128KB or so long. A text file.
>>
>>This is a "dir /S" listing of the folder I've got here. I could
>>probably cut it down to 4GB without too much trouble. The contents
>>are already compressed by Microsoft, so 7ZIP would not perform
>>miracles on the content.
>>
>>https://pastebin.com/XHqXVfh4
>
>What am I supposed to do with the Pastebin.com info? If I download
>from that page, what do I do with all that? It appears to me to a
>copy of what you have downloaded using WSUSOffline. Correct?
>>
>>UpdateGenerator.exe is what collects the downloads (the GUI).
>>client\UpdateInstaller.exe is what installs at the target machine
>>
>>You run UpdateGenerator on the healthy technician machine
>>and build a "kit".
>>
>>The "kit" is sent to the recipient, and they run UpdateInstaller.exe
>>on the order of five times. There is a reboot after each
>>partial install. The early stages ensure the support structure
>>is there for things to work. The last step loads in 150 or so
>>Windows Updates, one after another.
>>
>>*******
>Are you saying that I can run UpdateGenerator on my machine, and
>somehow send BIL the downloaded files? 8GB would take all day (
>longer) to "File Transfer" via Team Viewer. Or, could send them on a
>USB stick. Would he then just run UpdateInstaller and point it to the
>USB drive?
>>
>>The bare minimum you could do, is to use the chunk of code that
>>installs certificates and revokes, and give it a folder to work on.
>>
>>"DoUpdate.cmd" 78KB script, there is this chunk...
>>
>> rem *** Install Trusted Root Certificates and Certificate revocation lists ***
>> if "%UPDATE_RCERTS%" NEQ "/updatercerts" goto SkipTRCertsInst
>> echo Installing Trusted Root Certificates...
>> for /F "tokens=*" %%i in ('dir /B ..\win\glb\*.crt') do (
>> if exist %SystemRoot%\Sysnative\certutil.exe (
>> %SystemRoot%\Sysnative\certutil.exe -f -addstore Root "..\win\glb\%%i"
>> ) else (
>> %SystemRoot%\System32\certutil.exe -f -addstore Root "..\win\glb\%%i"
>> )
>> call :Log "Info: Installed ..\win\glb\%%i"
>> )
>> echo Installing Certificate revocation lists...
>> for /F "tokens=*" %%i in ('dir /B ..\win\glb\*.crl') do (
>> if exist %SystemRoot%\Sysnative\certutil.exe (
>> %SystemRoot%\Sysnative\certutil.exe -f -addstore Root "..\win\glb\%%i"
>> ) else (
>> %SystemRoot%\System32\certutil.exe -f -addstore Root "..\win\glb\%%i"
>> )
>> call :Log "Info: Installed ..\win\glb\%%i"
>> )
>> :SkipTRCertsInst
>
>Ok, if I put the above code into a folder, what do I do with it?
>>
>>The folder download list is this list, and you don't need Silverlight,
>>it just happens to be stuffed into the same leftovers folder with
>>the certs. This is the folder the previous chunk of code loops over.
>
>Silverlight was already installed somewhere along the line. May have
>been when I was manually installing DotNet 3.5 & 4.6 to get another
>proggy to install that required them. I remember you saying that
>other things should be done BEFORE DotNet installs. Could this be
>causing a problem?
>>
>>
>>StaticDownloadLinks-win-glb.txt
>>
>>https://download.microsoft.com/download/D/D/F/DDF23DF4-0186-495D-AA35-C93569204409/50918.00/Silverlight.exe
>>https://download.microsoft.com/download/D/D/F/DDF23DF4-0186-495D-AA35-C93569204409/50918.00/Silverlight_x64.exe
>>http://www.microsoft.com/pkiops/certs/Microsoft%20ECC%20Root%20Certificate%20Authority%202017.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20ECC%20Root%20Certificate%20Authority%202017.crl
>>http://www.microsoft.com/pkiops/certs/Microsoft%20RSA%20Root%20Certificate%20Authority%202017.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20RSA%20Root%20Certificate%20Authority%202017.crl
>>http://www.microsoft.com/pkiops/certs/Microsoft%20EV%20ECC%20Root%20Certificate%20Authority%202017.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20EV%20ECC%20Root%20Certificate%20Authority%202017.crl
>>http://www.microsoft.com/pkiops/certs/Microsoft%20EV%20RSA%20Root%20Certificate%20Authority%202017.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20EV%20RSA%20Root%20Certificate%20Authority%202017.crl
>>http://crl.microsoft.com/pki/crl/products/MicRooCerAut_2010-06-23.crl
>>http://www.microsoft.com/pki/certs/MicRooCerAut2011_2011_03_22.crt
>>http://www.microsoft.com/pkiops/certs/Microsoft%20Time%20Stamp%20Root%20Certificate%20Authority%202014.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20Time%20Stamp%20Root%20Certificate%20Authority%202014.crl
>>http://www.microsoft.com/pkiops/certs/Microsoft%20ECC%20Product%20Root%20Certificate%20Authority%202018.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20ECC%20Product%20Root%20Certificate%20Authority%202018.crl
>>http://www.microsoft.com/pkiops/certs/Microsoft%20ECC%20TS%20Root%20Certificate%20Authority%202018.crt
>>http://www.microsoft.com/pkiops/crl/Microsoft%20ECC%20TS%20Root%20Certificate%20Authority%202018.crl
>>
>>WSUSOffline includes a copy of wget.exe and it is a thing
>>that can "eat" http: links like those and get them for you.
>>You can put the word "wget.exe" in front of each link, etcetera,
>>and make a .bat file if you want. The files seem relatively small
>>for some reason. And perhaps those aren't really the "meat".
>>But they're binary inside, those files, and I can't tell if
>>they're pointers or merely a means to bootstrap the
>>acquisition of the real thing (actual certificate files).
>>
>>*******
>
>If I understand the above right, I can download all the links to BIL's
>machine and manually install all those updates? What then? Run
>WSUSOffline again?
>>
>>One of the "benefits" of running the entire update process
>>of WSUSOffline, is it outputs log info into the command prompt
>>window it uses. And any failure messages could help indicate
>>what isn't working. Thus, it's not entirely about just
>>updating, the process is also intended to be indicative of
>>installation health.
>
>I did look at the log file after it failed verification, but didn't
>see anything that pointed to a "smoking gun". It didn't look like it
>was that large a file, so I can post it to a file share if you'd like
>to see it.
>>
>>But it's a damn nuisance to send a thing like that to
>>another person, as it might take a rather large dual layer
>>DVD to do it, or a USB stick, and sending it by mail. If
>>you "collect" at your end, your upload rate on the Internet
>>service is going to throttle how fast you can get it
>>to the remote "target" storage folder.
>>
>>BTW - Did using Firefox on the target machine and doing the
>> ssllabs command on "walmart.com" indicate anything interesting ?
>
>Since he doesn't use Firefox I was hesitant to install it. If you
>think it would help I can always remove it when done.
>
>On a personal note. I'm really hesitant to "look a gift horse in the
>mouth", but as I said earlier, while I really appreciate all the info
>given, sometimes it completely overwhelms me since I don't understand
>so much of it. I'm 80 years old and don't plan on starting coding
>anytime, so a simple step by step approach (i.e. do this then this)
>would work much better for me. :-)
>
>Thank you so very much for sticking with me through all this! Very
>much appreciated.
>>