Windows 10 update not installing KB3081424

Cumulative Update for Windows 10 for x64-based Systems (KB3081424) FAILED and took forever to uninstall?

Downloads, reboot to install.
Gets to 30% and reboots.
Gets yo 59% and reboots.
Gets to 59% again and then states something went wrong so uninstalling the update.
Wait a few minutes and reboot.
Back to login screen.



Here an unofficial fix, use at your own risk and backup the registry keys before removing!
Only do this if you know what your doing:


Basic guide (detailed right down the bottom of this page)
  • Create system restore point and export/backup any keys deleted
  • Remove SID's for users (not system accounts) that no longer exist in the registry
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
  • Check which users don't exist by checking computer management/local users and groups/users.

Direct links for the update:

x86
http://download.windowsupdate.com/d/msdownload/update/software/crup/2015/08/windows10.0-kb3081424-x86_74cacb95454c2b7160e4652fc3816d5bb57023e8.msu
x64
http://download.windowsupdate.com/d/msdownload/update/software/crup/2015/08/windows10.0-kb3081424-x64_166daaea0dfeb06b34f39d7aebf03ff93a7bf99e.msu



DETAILED INSTRUCTIONS


Do this at your own risk, editing the registry can stop your pc from working altogether

Be aware that there are almost bound to be some exceptions where these instructions don't work

Open regedit

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Double click the key/folder icon to see the contents.
You should see at least 5 keys with the names:
S-1-5-18
S-1-5-19
S-1-5-20
S-1-5-21-(massive long number here)
S-1-5-21-(different massive long number here)

If you don't have at least two entries that begin S-1-5-21- then close the registry editor and look elsewhere for a solution to your problem.

If you have more than one entry beginning S-1-5-21 then open each one in turn at look at the data for the key ProfileImagePath, It should say something like 'C:\Users\fred'

Open File Explorer and navigate to the C:\Users folder (assuming C is the drive letter in the ProfileImagePath data). You will see several folders there but you should see one called 'fred'

Keep doing this until you find an S-1-5-21-(something) key for which there is no corresponding actual folder .

Before you do anything else, type System Restore into the search box.  You should see 'Create a restore point Control panel'.  Click that and a System Properties window should open at the System Protection tab.  Click create and enter a name in the box (I entered 'manual') then click create.  After a while you should get a message 'A restore point has been created successfully'.

Now take the life of your computer in your hands
Go back to Registry editor, Right click the S-1-5-21-(something) key for which there is no corresponding actual folder

(Left) click delete from the drop-down menu

Get this wrong and your computer might not start or one of the user accounts you wanted will be lost. If it goes wrong, your best hope is to run System Restore and try to go back to the restore point you created.


But if it works there is a good chance the update will now install!

How To Find the WiFi Password on Mac OS X


#1: Display the WiFi Password on Mac OS X Using CLI

You can use the security command. It is a command line interface to keychains and Security framework which stores your WiFI password and other information. Open the Terminal app and type the following command:

security find-generic-password -ga YOUR-ACCOUNT-NAME
security find-generic-password -ga SSID-HERE
security find-generic-password -ga YOUR-WiFi-Access-Point-Name-Here

In this example, find the Wifi password for Iphone4s access point (SSID):

security find-generic-password -ga Iphone4s | grep -i password


security find-generic-password -ga Iphone4s

#2: Not a Fan of Command Line Tools? 

The System Keychain is a utility which securely stores all passwords and user IDs for a user and lets that user unlock them all with a single master password.
System Keychain Location
◾Open Spotlight to start a search by pressing Command (⌘)-Space bar
◾In the search field type: keychain access


Try this for Linux / Ubuntu

cat /etc/NetworkManager/system-connections/ | grep psk



How to Kill a Desktop Application or Background Process on Linux

Source URL Howtogeek


Windows has Ctrl+Alt+Delete and Macs have Command+Option+Escape to force frozen applications to close. Linux has its own ways of “killing” those misbehaving processes, whether they’re graphical windows or background processes.
The exact graphical tools you can use will depend on your desktop environment, as eachdesktop environment brings different tools to the table. But most of them are pretty similar.

From a Graphical Desktop

Modern Linux desktops deal with this fairly well, and it can be surprisingly automatic. If an application isn’t responding, a desktop with a compositiong manager will often gray the entire window out to show it isn’t responding.
Click the X button on the window’s titlebar and the window manager will often inform you that the window isn’t responding. You can either give it some time to respond or click an option like “Force Quit” to foricbly close the application.
On Linux, the window manager that paints the title bars is separate from the application itself, so it usually responds even if the window won’t. Some windows do paint their own interfaces, though, so this may not always work.
The “xkill” application can help you quickly kill any graphical window on your desktop.
Depending on your desktop environment and its configuration, you may be able to activate this shortcut by pressing Ctrl+Alt+Esc. You could also just run the xkill command — you could open a Terminal window, type xkill without the quotes, and press Enter. Or, you could press a shortcut like Alt+F2, which opens the “Run Command” dialog on Ubuntu’s Unity desktop and many others. Type xkill into the dialog and press Enter.
Your cursor will change to an X. Click a window and the xkill utility will determine what process is associated with that window, and then immediately kill that process. The window will instantly vanish and close.
Your Linux desktop probably has a tool that works similarly to the Task Manager on Windows, too. On Ubuntu’s Unity desktop, GNOME, and other GNOME-based desktops, this is the System Monitor utility. Open the System Monitor utility to see a list of running proesses — including background ones. You can also forcibly kill processes from here if they’re misbehaving.

From the Terminal

RELATED ARTICLE
How to Manage Processes from the Linux Terminal: 10 Commands You Need to Know
The Linux terminal has a number of useful commands that can display running processes, kill them, and change their priority... [Read Article]
Let’s say you want to do this all from the terminal instead. We covered a lot of the utilities you can use for this when we looked at commands for managing processes on Linux.
Let’s say Firefox is running in the background and we want to kill it from the terminal. The standard kill command takes a process ID number, so you’ll need to find it first.
For example, you could run a command like:
ps aux | grep firefox
Which would list all processes and pipe that list to the grep command, which will filter it and print only lines containing Firefox. (The second line you’ll see is the grep process itself.) You can also get the process ID from the top command and many other places.
Take the process ID number from the Firefox process — just to the right of the username — and provide it to the kill command. That is, run the command like so:
kill ####
If the process is running as another user, you’ll need to become the root user first — or at least run the kill command with the sudo command, like so:
sudo kill ####
That’s a basic method, but it isn’t quite the fastest. The pgrep and pkill commands help streamline this. For example, run “pgrep firefox” to see the process ID of the running Firefox process. You could then feed that number to the kill command.
Or, skip all that and run “pkill firefox” to kill the Firefox process without knowing its number. pkill performs some basic pattern-matching — it’ll try to find processes with names containing firefox.
The killall command is like pkill, but a bit more precise. It’ll kill all running processes with a specific name. So running “killall firefox” will kill all running processes named “firefox,” but not any processes that just have firefox in their names.

These are far from the only commands included on Linux for managing processes. If you’re using some type of server administration software, it may also have helpful ways to kill and restart processes.
System services work different from processes — you’ll need to use specific commands to bring down, restart, or bring up services. Those specific commands can be different on different Linux distributions.
Image Credit: Lee on Flickr