Am I the only winfag who didn't recive meltdown update? Why? Is my windows update service fucked up again? Enterprise 64bit activated by KMSPico.
Am I the only winfag who didn't recive meltdown update? Why? Is my windows update service fucked up again...
Do you use any AV?
uninstalled mbam and still up to date
good thing that this shit never came to my computer
What's your windows 10 build? 1709?
>single core 1.0 Ghz intel atom
Feels good somehow
Server 2016 here, did not receive update yet. However I have been holding off rebooting from previous updates by fu*king up the 'reboot' file from updateochestrator.
this. a slightly higher resolution would be nice tho.
I did get the update but did not install it yet as googling the update ID showed some forum threads and articles stating how it fucks your system up
>Windows 7
>Not seeing the update
>No idea if MSI will be updating my motherboard
Getting real sick of this shit.
same fucking here
Follow instructions on . Your Intel CPU microcode will be updated on the OS level. Don't wait for the BIOS update that will never come.
What does it mean?
probably that the update that adds that command isnt installed.
You need to download it first with the get command.
you need to:
Set-ExecutionPolicy Bypass
Install-Module SpeculationControl
Set-ExecutionPolicy Restricted
and then
Get-SpeculationControlSettings
yes
a microcode update will probably be shipped through windows update, like it has always been
My last two updates are KB4056887 on the 10th January and KB4058043 on the 17th December. Just checked for updates right now, nothing. Looks like MS doesn't give a fuck about me lol.
...
>installing a script from an untrusted repository
wew
I had to install it manually from the windows update catalog, since it wouldn't show up even though I have no AV anymore.
You can "Uninstall-module [Name of the script]" after that faggot
>implying the damage hasn't been done
this is why i don't use ganoo. who knows what malicious code n*rds are writing
>unable to read and understand a very verbose error message
>the absolute state of winfags
Verifying that protections are enabled
To help customers verify that protections are enabled, Microsoft has published a PowerShell script that customers can run on their systems. Install and run the script by running the following commands.
Note These verification steps only apply to Windows client and not to Azure instances. For further cloud guidance, see the Azure blog.
PowerShell Verification using the PowerShell Gallery (Windows Server 2016 or WMF 5.0/5.1)
Install the PowerShell Module
PS> Install-Module SpeculationControl
Run the PowerShell module to validate the protections are enabled
PS> # Save the current execution policy so it can be reset
PS> $SaveExecutionPolicy = Get-ExecutionPolicy
PS> Set-ExecutionPolicy RemoteSigned -Scope Currentuser
PS> Import-Module SpeculationControl
PS> Get-SpeculationControlSettings
PS> # Reset the execution policy to the original state
PS> Set-ExecutionPolicy $SaveExecutionPolicy -Scope Currentuser