Installing chocolatey Win10 32bit Command Prompt

Installing chocolatey Win10 32bit Command Prompt
Successful installation

Installing chocolatey Chocolatey v0.10.15 Win10 32bit Command Prompt

Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
Getting latest version of the Chocolatey package for download.
Getting Chocolatey from https://chocolatey.org/api/v2/package/chocolatey/0.10.15.
Downloading 7-Zip commandline tool prior to extraction.
Extracting C:\Users\USER_NAME\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip to C:\Users\USER_NAME\AppData\Local\Temp\chocolatey\chocInstall...
Installing chocolatey on this machine
Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
Restricting write permissions to Administrators
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
WARNING: Not setting tab completion: Profile file does not exist at
'C:\Users\USER_NAME\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'.
Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder

Testing chocolatey installation on Win10 32bit

C:\WINDOWS\system32>choco
Chocolatey v0.10.15
Please run 'choco -?' or 'choco <command> -?' for help menu.

Upgrading chocolatey installation on Win10 32bit

C:\WINDOWS\system32>choco upgrade chocolatey
Chocolatey v0.10.15
Upgrading the following packages:
chocolatey
By upgrading you accept licenses for the packages.
chocolatey v0.10.15 is the latest version available based on your source(s).

Chocolatey upgraded 0/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

HP Probook 4540s Win 10 32 bit drivers problem

HP Probook 4540s Win 10 32 bit drivers problem

HP Probook 4540s driver problem win 32 bit

When you attempt to ask HP for drivers for your HP Probook 4540s notebook you navigate here, but you unfortunately you don't find anything useful in this page, because :

HP doesn't support certain products and notebook models ever since win 10 released. 

HP Probook 4540s driver problem win 32 bit doesn't exist

 also, if you click on (I don't see my operating system) you learn that :

Nonsense

If you do not see the version of your operating system (OS) listed, HP does not have any downloadable software or drivers for your product.

Many issues can be resolved by ensuring that you have both the latest OS version supported for your HP product and the latest HP driver updates. HP recommends that you install all updates from your OS vendor.

CAUTION:

Recently, HP has seen an increased number of third-party support websites selling HP driver downloads or diagnostic tools. Many of these websites use the HP trademark symbol and claim to be official HP distributors. If your product supports your operating system, HP offers your driver and software at no additional cost through the HP website. Use caution when dealing with any website that asks you to pay for HP driver downloads or tools that claim to diagnose your HP products. These websites might not be affiliated with HP in any way. 

Do not install BIOS updates from a motherboard manufacturer's website. Only install BIOS updates from HP. Installing BIOS updates from the motherboard manufacturer can prevent the computer from accepting an HP system recovery. This could result in a loss of data.

Solution

As they stated in HP, that all of the products not supported by HP can only be supported by WindowsUpdate. So we are waiting.

Windows 10 Internet Connection Sharing ICS hung on starting - Solved

 Windows 10 Internet Connection Sharing ICS hung on starting

 Windows 10 Internet Connection Sharing ICS hung on starting

my ICS service is hung on starting, it was working fine last night when I went to bed, It updated while i was sleeping and now ICS wont start at all, and i need it to for the way my network is setup. I've checked all the dependencies and they are all running, Windows Firewall is also running fine, I just cant share my internet connection to my network anymore.

I've tried sfc scan in command prompt, ive tried manually killing and restarting the service but it will not work, it says "The service is taking too long to start." it doesn't actually hard fail it just hangs there. I have a 9 year old son with autism that uses this network to watch his cartoons in his room when he gets off the bus, I need to get this fixed. I even tried to just reset my PC, but it tells me my password is invalid which is 100% BS because its the same password and account im using right now to post this question. 

Solution:

1) Settings -> Update and Security -> 

 

2) Open Windows Defender -> 

 

 

3) Open Windows Defender Security Center -> 

 

4) Open Firewall and Network Protection -> 

 

5) Restore Firewall default settings