On Mon, 19 Sep 2022 15:37:24 -0400, Paul <nospam@needed.invalid>
wrote:

>On 9/19/2022 12:20 PM, jetjock wrote:
>> On Mon, 19 Sep 2022 11:17:54 -0500, jetjock <jetjock@unkown.com>
>> wrote:
>>
>>> On Sun, 18 Sep 2022 18:44:55 -0400, Paul <nospam@needed.invalid>
>>> wrote:
>>>
>>>> On 9/18/2022 5:10 PM, jetjock wrote:
>>>>> On Sun, 18 Sep 2022 16:03:40 -0500, Paul in Houston TX
>>>>> <Paul@Houston.Texas> wrote:
>>>>>
>>>>>> jetjock wrote:
>>>>>>> I got sick of Win 8.1 on my old Dell Inspiron 15 and put Win 7
>>>>>>> Ultimate back on it. After deleting all the GPT partitions down to
>>>>>>> one, Windows installed ok. Unfortunately, it is just that; Windows 7!
>>>>>>> There is no Ethernet Controller, Network Controller, PCI Simple
>>>>>>> Communications Controller, SM Bus Controller, Universal Serial Bus
>>>>>>> Controller or USB2.0 Controller.
>>>>>>>
>>>>>>> I tried installing WSUS Offline updates, but it said it couldn't
>>>>>>> download things. So much for "offline"! I have tried installing
>>>>>>> drivers for the various ones missing by pointing the device manager
>>>>>>> driver updater at every Intel, x64 and other driver package I have,
>>>>>>> but it keeps telling me that it can't find a driver for the item. A
>>>>>>> couple times it did say that the driver it found might not work
>>>>>>> correctly but I could install it anyway. I choose not to.
>>>>>>>
>>>>>>> I downloaded the Intel Trusted Execution Engine Interface Driver to
>>>>>>> my desktop from the Dell Website. Tried to install it on the laptop
>>>>>>> and was told that "The procedure entry pointADDDLLDirectory could not
>>>>>>> be located in the dynamic link library KERNEL32.dll.
>>>>>>>
>>>>>>> I'm out of ideas. Paul, (or anyone) can you help me out?
>>>>>>
>>>>>> Did you try the genuine drivers from Dell?
>>>>>> https://www.dell.com/support/home/en-us/product-support/product/inspiron-15-3555-laptop/drivers
>>>>>
>>>>> Not that page, per se, but every driver I got from them for a 3510 (I
>>>>> think that's what mine is) is newer than what's on that page. They all
>>>>> give that same error of not finding the entry point.
>>>>>
>>>>> >>>>>>>>>>jetjock<<<<<<<<<<
>>>>>
>>>>
>>>> I would work on getting a network driver to the machine, so that
>>>> the rest of the Genuine Drivers can be downloaded directly on the
>>>> machine.
>>>>
>>>> Realtek Ethernet Controller Driver Version 7.94.723.2015, A00
>>> I was finally able to get the correct network driver for my machine
>>>from the Dell Website and am now running WSUS Offline.
>>>>
>>>> You might want to bring over a Firefox installer (or whatever
>>>> your favorite non-MSFT browser is), so the Dell website will not
>>>> fight you while you work. IE11 or other versions of IE, would
>>>> make a poor "bootstrap" browser right now.
>>>
>>> Will install FF as soon as WSUS is finished
>>>>
>>>> There's no chipset driver mentioned on the Dell site.
>>>> A PDF for your machine says it's not an Intel, and uses AMD instead.
>>>> It's like shopping at KMart or the Dollar store, we have to know
>>>> which store we're headed to :-)
>>>
>>> My computer is a Dell 5558 and it does have an Intel Core I7
>>> processor
>>>>
>>>> System information
>>>> Computer model Inspiron 15-3555
>>>>
>>>> Processor
>>>> AMD E1-6010 APU with Radeon R2 Graphics
>>>> AMD E2-6110 APU with Radeon R2 Graphics
>>>> AMD A6-6310 APU with Radeon R4 Graphics
>>>> AMD A8-7410 APU with Radeon R5 Graphics
>>>> Chipset Integrated in processor [hah!]
>>>>
>>>> You can Google for "A8-7410 chipset driver". Insert actual CPU name.
>>>> I just picked one and ran with it.
>>>>
>>>> https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-6-1-win7
>>>>
>>>> AMD Software: Adrenalin Edition 22.6.1 Driver for Windows 7 64-bit
>>>>
>>>> https://drivers.amd.com/drivers/radeon-software-adrenalin-2020-22.6.1-win7-64bit-june23-2022.exe
>>>>
>>>> Most of that is the graphics driver (just select the graphics driver part,
>>>> the whole gamer package is overkill for most usages and also gathers metrics
>>>> about your usage, and the metrics waste disk space). There should be tick
>>>> boxes, and you can switch off the sludge.
>>>>
>>>> But there is a chipset driver section. That's useful for tidying the
>>>> Device Manager a bit.
>>>>
>>>> And what you're doing, will be hard work. I can't take
>>>> the hardness out of the work, unfortunately. You're in for
>>>> a driver slog.
>>>>
>>>> I hope you installed from Win7 SP1 media, as that's a start.
>>>
>>> Version installed is Win 7 Ultimate x64 with SP 1.
>>>>
>>>> And the WSUSOffline is still recommended. A network driver, and
>>>> the in-box hard drive storage driver, may be enough to do your
>>>> 170 updates with your WSUSOffline USB stick. WSUSOffline will
>>>> do its best in terms of Windows Update configuration. It does not
>>>> try to install MSFT crapware if it can get by without it.
>>>>
>>>> It may be looking for a current wsusscn2.cab file. I don't know
>>>> if the signing on that is the best. Which is why WsusOffline has to
>>>> install the SHA2 patches first, so the "calculating updates" phase
>>>> will actually work. It does not just use a dumb "install everything"
>>>> method, it actually computes what is needed, using facilities on
>>>> the machine.
>>>>
>>>> That .cab file, tools do not generally like to use it, if it is
>>>> more than 24 hours old.
>>>>
>>>> I'm heading out the door, or I'd do more research...
>>>
>>> I ran WSUS v1.9 but got a "signature verification failure:
>>>
>>> Mon 09/19/2022 10:44:56.30 - Info: Starting WSUS Offline Update
>>> download v. 11.9 for w61-x64 glb
>>> Mon 09/19/2022 10:44:56.33 - Info: Option /includedotnet detected
>>> Mon 09/19/2022 10:44:56.39 - Info: Option /seconly detected
>>> Mon 09/19/2022 10:44:56.45 - Info: Option /verify detected
>>> Mon 09/19/2022 10:44:56.50 - Info: Option /exitonerror detected
>>> Mon 09/19/2022 10:44:56.81 - Info: Set time zone to LOC7:00
>>> Mon 09/19/2022 10:44:57.30 - Info: Preserved custom language and
>>> architecture additions and removals
>>> WARNING: cannot verify download.wsusoffline.net's certificate, issued
>>> by 'CN=R3,O=Let\'s Encrypt,C=US':
>>> Unable to locally verify the issuer's authority.
>>> 2022-09-19 10:44:58
>>> URL:https://download.wsusoffline.net/StaticDownloadFiles-modified.txt
>>> [71/71] -> "../static/StaticDownloadFiles-modified.txt" [1]
>>> WARNING: cannot verify download.wsusoffline.net's certificate, issued
>>> by 'CN=R3,O=Let\'s Encrypt,C=US':
>>> Unable to locally verify the issuer's authority.
>>> 2022-09-19 10:44:59
>>> URL:https://download.wsusoffline.net/ExcludeDownloadFiles-modified.txt
>>> [0/0] -> "../exclude/ExcludeDownloadFiles-modified.txt" [1]
>>> WARNING: cannot verify download.wsusoffline.net's certificate, issued
>>> by 'CN=R3,O=Let\'s Encrypt,C=US':
>>> Unable to locally verify the issuer's authority.
>>> 2022-09-19 10:45:00
>>> URL:https://download.wsusoffline.net/StaticUpdateFiles-modified.txt
>>> [0/0] -> "../client/static/StaticUpdateFiles-modified.txt" [1]
>>> Mon 09/19/2022 10:45:00.40 - Info: Updated static and exclude
>>> definitions for download and update
>>> Mon 09/19/2022 10:45:00.45 - Info: Restored custom language and
>>> architecture additions and removals
>>> Mon 09/19/2022 10:45:02.26 - Info: Downloaded/validated mkisofs tool
>>> Mon 09/19/2022 10:45:03.96 - Info: Downloaded Sysinternals' tools
>>> Autologon, Sigcheck and Streams
>>> Mon 09/19/2022 10:53:35.23 - Info: Downloaded/validated most recent
>>> Windows Update catalog file
>>> Mon 09/19/2022 10:54:37.79 - Warning: Deleted unsigned file
>>> 'E:\wsusoffline\client\wsus\wsusscn2.cab'
>>> Mon 09/19/2022 10:54:37.87 - Error: Catalog file
>>> ..\client\wsus\wsusscn2.cab signature verification failure
>>>
>>> Any suggestions?
>>>
>>>> Paul
>>>
>>> >>>>>>>>>>jetjock<<<<<<<<<<
>>
>> Version should have read 11.9--not 1.9
>>
>> >>>>>>>>>>jetjock<<<<<<<<<<
>>
>
>I suspect we may be talking about more than one computer here.
>
> Info: Starting WSUS Offline Update download
>
>I also think you did not see my other post.
>
>http://al.howardknight.net/?STYPE=msgid&MSGI=%3Ctg92lc%24110ig%241%40dont-email.me%3E
>
> UpdateGenerator.exe # Needs network, downloads and collects updates, to be used later by you
> # You do this work on your Technician Machine, and
> # before visiting the "desperate" machine with your "catch".
>
> client\UpdateInstaller.exe # Does not need network. Uses the wsusscn2.cab file collected during
> # the other step. When IE11 installs, the IE11 window will open and it
> # will attempt to contact msn.com for the home page (or whatever). This
> # network activity is non-blocking, can be ignored, and IE11 dismissed.
> # UpdateInstaller.exe patches up the "desperate" machine which
> # received the new Win7 installation.
>
>The LetsEncrypt symptoms are reminiscent of a WinXP machine. A few months
>back, a number of WinXP users were almost cut off from the Internet,
>by a problem caused by all the https servers using LetsEncrypt certificates.
>Those are free certificates that even sites like Eternal-September used.
>LetsEncrypt was part of the "HTTPS (TLS) Everywhere" campaign. It is possible
>to patch up Windows XP and make it work again. People who have *one* computer,
>with WinXP on it, if the LetsEncrypt event were to happen today, they'd
>have to use a public library computer and a USB stick, to escape the shackles.
>If you have more than one computer, you should be able to repair Windows XP
>and make the network work (well enough) again.
>
>I think you were on the Technician machine and running UpdateGenerator.exe .
>
>Once Wsusoffline has acquired a file set (could be 7GB worth), you visit
>the destination machine and install using the second command.
>
>Steps:
>
>1) Start your work, on the Technician machine. This is a machine with a
> working OS, with modern facilities on board. A working certificate store
> would be part of a Technician machine OS. WinXP is kinda old for maintenance
> work now.
>
> UpdateGenerator.exe # 7GB of downloads
> # the updates will be stored in the folder the
> # tools are in.
>
>2) Copy the 7GB folder (all of wsusoffline\ ), using a USB stick for carriage.
> A USB stick allows you to walk a network driver over to the target machine
> as well. As even if Wsusoffline install step worked, you still would not
> have a working network.
>
> Once at the target machine, using an account with Administrator privilege
> (the account made when you installed Windows 7). you run
>
> client\UpdateInstaller.exe # Only tick the tick boxes needed
>
>And after five reboots or so, it might be updated to some
>degree of completion. Maybe ten or so (some jumbo) updates left.
>
>The reason WinXP isn't going to be a good Technician Machine, is the
>certificate store on WinXP won't receive updates. Some of the OSes
>check either daily or check weekly, for certificate store changes.
>
>Firefox has its own certificate store. However, the wsusoffline uses
>onboard FOSS tools like "wget.exe" to fetch files, and it might be
>relying on the OS certificate store and SChannel for services or something.
>Not too many tools keep private certificate stores.
>
>What OS is on the Technician Machine, where you are preparing your
>wsusoffline folder with the Windows 7 files expected ?
>
>You have to "fill up" the wsusoffline folder, before taking it over to the
>"machine in desperate need of help". And the reason we're doing this,
>is for the early phases of Wsusoffline, which repairs Windows Update
>and get it working properly, without the user lifting a finger.

Paul,

Thanks for the detailed instructions. I was not aware that two
machines were required, I have it running on my desktop (technicians
machine) now and will then try running the downloaded files on the
laptop in question (client machine).

What boxes would you recommend ticking?

>>>>>>>>>>jetjock<<<<<<<<<<