- Jul 1, 2017
- 1,396
@Klappis My bad my bad. When the forums migrated it disappeared. Just made a new one. Thanks for the headsup.
Why do I get a warning saying Requires standard user account?+EOPRadar
It checks which running programs can pose a risk of escalation of privilege. It's worth running once in a while to see which processes pose EOP risks.
Windows Apps by FS1
You need to run it as a SUA to test it. If your default account is an admin account it won't work because by definition you are at risk of privilege escalation at every corner I think.Why do I get a warning saying Requires standard user account?
Adding 0patch as well.Added
+0patch
Cannot wait for Microsoft to fix these task scheduler issues that only require bytes of code. There are also patches for 7-zip as well.
Download here:Oct 27, 2018
HPSBHF03584 rev. 7 - Derivative Side-Channel Analysis Method
Derivatives of speculative execution side-channel analysis methods publicly disclosed in January 2018 can be exploited to facilitate the unauthorized exposure of privileged data from memory.
More information is available at the following links:
- Intel’s Security Advisory (in English)
- AMD’s Security Advisory (in English)
Let others test HP BIOS first and if everyone says its okay to install then go ahead. Keep a HP BIOS recovery USB in hand before updating BIOS.Owners of HP laptops, there is a new BIOS Update available that is not shown on the Support/Driver pages of your device:
Download here:
HPSBHF03584 rev. 7 - Derivative Side-Channel Analysis Method | HP® Customer Support
tl:dr It will update your Intel microcode to the one released in June 2018 which is more efficient, stable and more secure.
Nice. Any reasons why you updated to v1809?+Updated to Windows 10 1809
The new update has all the fixes that I needed.
They fixed IPv4 so Windows Store and other important programs work when you disabled IPv6. I did an in-place upgrade and ran into the following issue: "We couldn’t update system reserved partition"
Microsoft provided a solution on their support page but it didn't do enough so I revised them for anyone who might see this on the wild Internet:
I had to delete like 10 folders before I finally had enough space to install Windows.
- First of all backup backup backup even if you think you won't ever go back to the older version this will save you. Make sure to back up all partitions no matter how small, especially the SYSTEM partition.
- Right click Start. Choose Windows Powershell (Admin).
- In Powershell, type mountvol y: /s and then hit Enter. This will add the Y: drive letter to access the System Partition.
- Switch to the Y drive by typing Y: and press Enter. Then, navigate to the Boot folder by typing cd EFI\Microsoft\Boot. Once there, type ls to list the folders available. You will see a lot of language packs (en-US, es-ES, de-DE, en-GB, etc). Delete them one by one with the command del *folder-name* for example del en-US. The system may ask you if you are sure to continue, press Y and then Enter to continue. Delete a handful of these language pack folders or more. Then click on setup.exe in your iso file and try to install again. If you still run into this issue, continue deleting language packs other than yours.
My pessimism about Microsoft. I don't think it's getting any better from here. lmaoNice. Any reasons why you updated to v1809?
I always used Boot repair ISO or Linux to delete them manually, Win PE asks too many questions.
I won't upgrade for 2 years. I don't have time for incremental updates.My pessimism about Microsoft. I don't think it's getting any better from here. lmao
Oh I see what you mean now. Well while their new features are meh and buggy, the new builds also make various improvements to security out of the box that they don't really mention and I think it works a little better at recognizing 3rd party security software.I won't upgrade for 2 years. I don't have time for incremental updates.