How to fix the “Your computer is low on memory” Windows 10 error message

šŸŽ¶ If you’re having RAM problems I feel bad for you son šŸŽ¶

Ever gotten the error message below?

c37da72e%2d7ed0%2d41a4%2db972%2d188ba5faa332

Your computer is low on memory

To restore enough memory for programs to work correctly, save your files and then clsoe or restart all open programs.

The root cause may be a poorly behaving service installed with Realtek network drivers calledĀ RunSWUSB. Disabling it should fix the issue. Here’s how to do that:

  1. Open the Start Menu.
  2. Type Services.
  3. In the window that pops up, find RunSWUSB.
  4. Right-click on the above entry.
  5. Click Stop if it isn’t greyed out.
  6. Click Properties.
  7. In the window that pops up, under the General tab, click the Startup type: dropdown menu.
  8. Click Disabled.
  9. Click Apply.
  10. Click OK.
  11. Close Services.

So how’d I figure this out? First of all, it seems to be rare; only 1 of my 3 Windows 10 PCs was afflicted with it. The PC that was having this issue is running Windows 10 Insider Slow Ring and was experiencing errors during the build update process. As part of the steps to resolve those, I performedĀ a clean boot. After the update process successfully completed, I went through disabled services individually to see which were worth re-enabling. Googling this particular one produced this thread about its associated memory leak problems.

If the above doesn’t fix the problem, try performing a clean boot. Then do the following:

  1. Open the Start Menu.
  2. Type msconfig.
  3. Hit Enter.
  4. In the window that pops up, click theĀ Services tab.
  5. Check theĀ Hide all Microsoft services box.
  6. Google each remaining service individually to figure out what it does. You may find the culprit eventually.
  7. When you do find it, disable it as previously shown.
  8. Add the offending service to the Microsoft support thread so your findings can help others!

Thanks cartman82 for the fix!

How to resolve Error 0x80240fff when installing Windows Insider Builds

Solving problems by turning 1 incomprehensible error into 2 more manageable ones. I thought this only happened to Linux users.

Recently I was trying to update a Sony Vaio Fit 15E laptop from Windows Insider Slow Ring build 14931 to 14965 via Windows Update. The update would complete downloading and commence installing, but would fail during the multiple reboot process, causing the previous build to be restored.

After ensuring I had no SD cards inserted or USB devices attached, here are the steps I took to resolve it:

Defering Feature Updates

  1. OpenĀ Settings.
  2. ClickĀ Update & Security.
  3. ClickĀ Advanced Options.
  4. Check theĀ Defer feature updates box.
  5. Retry the update process.

That didn’t work, so I tried:

Running the Windows Update Troubleshooter

  1. OpenĀ Control Panel.
  2. In theĀ View by: dropdown, selectĀ Small icons.
  3. ClickĀ Troubleshooting.
  4. ClickĀ Fix problems with Windows Update.
  5. Follow the onscreen instructions to fix any problems that are found.
  6. Retry the update process.

That didn’t work either, so I tried:

Deleting theĀ C:\$WINDOWS.~BT folder

  1. Open File Explorer.
  2. Click theĀ View tab.
  3. Check theĀ Hidden items box in theĀ Show/hide ribbon section.
  4. Navigate to the C:\ drive.
  5. Delete the $WINDOWS.~BT folder.
  6. Retry the update process.

That didn’t work either, so I tried deferring feature updates again and rerunning the update process, producing this error:

There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800705b4)

So I tried:

Installing from the ISO instead

  1. Download the latest Slow Ring ISO here. You’ll need to sign in 1st so the page knows you’re a Windows Insider.
  2. Using WinRAR, 7-Zip, or a similar archive extraction tool, extract the ISO file to a folder.
  3. Open the above folder.
  4. Launch theĀ setup file.
  5. Set the installer to keep your apps, files, and settings and let it run.

That didn’t work either, so I tried deleting theĀ C:\$WINDOWS.~BT again and trying to install from ISO as above. This time I got this error:

0x8007042B – 0x4000D The installation failed in the SECOND_BOOT phase with an error during the MIGRATE_DATA operation

Although this error might seem disappointing, it was actually encouraging because it was the 1st one I’d gotten that actually explained what the issue was.

Googling the error produced this excellent post by Andre Da Costa. I had to:

  1. Do a clean boot (see link for instructions. It’s generally a good idea at all times – error or not – to enable clean boot before rebooting from your current build to install the new one. This will prevent existing startup processes from interfering with the installation.)
  2. Disconnect the laptop from the internet (disable Wi-Fi, unplug Ethernet cable.)
  3. Disconnect all non-essential USB peripherals, including mice if you have a working laptop touchpad.
  4. Reboot.
  5. Retry updating from the ISO files.

This finally fixed the issue.

Note that if you have any services or apps you’d prefer to run at startup, you’ll need to manually re-enable them via some combination of Task Manager, System Configuration, and Services.

I hate that the Insider build update process is this unreliable, but issues can be worked around with tenacity and thought.

Thanks to Microsoft employee /u/zac_l for his assistance on this Reddit support thread:

How to install the latest emoji on Windows

If only it were this easy in Android.

Like Android, Windows emoji are updated along with the OS. However, installing new emoji on Windows is much easier because Windows provides a GUI method for installing fonts within the OS itself. Here’s how to do it:

  1. Download the Windows archives for EmojiOne and/or Twitter Emoji for Everyone.
  2. Decompress the archives.
  3. In the decompressed folder(s), right-click the .ttf file.
  4. Click Install.

And that’s literally it. I used the above method on Windows 10; your mileage may vary on other versions.

Want those emoji on Android? Do this.

21% of developers are already on Windows 10

Windows 10 is booming among devs.

Stack Overflow recently publised their (annual?) developer survey, in whichĀ 56,033 coders in 173 countries participated.

When asked about their desktop OS, the participants responded as below in 2015 and 2016:

Windows1
No Windows 10 in 2015
Windows2
Windows 10 at 21% in 2016

Stack Overflow’s conclusion was, predictably as always for the blogosphere, negative for Windows:

If OS adoption rates hold steady, by next year’s survey fewer than 50% of developers may be using Windows.

Ummm yeah. Let’s just ignore Windows 10 – a single version of Windows – going from nothing to 1 in 5 developers in about half a year.

Let’s just ignore Windows 10 – a single version of Windows – going from nothing to 1 in 5 developers in about half a year.

Developer buy-in is crucial for any OS, as without developers there are no apps. The fact that devs are familiarizing themselves with the OS and using it for mission critical applications is extremely encouraging.

Windows 10’s growth among developers is nothing short of impressive. “If OS adoption rates hold steady,” it should be the #1 OS among developers in 2017.

Other Microsoft technologies made excellent showings in their respective categories; most notably Visual Studio and F#.

How to fix Windows 10 Technical Preview Build 9860 Action Center warnings about AVG Antivirus FREE 2015

Hint: you’ll have to reinstall AVG. Excited yet?

UPDATE: This problem appears to be fixed in Build 9879, albeit not in the way one might expect. That build blows cripples AVG – and, presumably, all other 3rd party AV apps – away and replaces them with Windows Defender. AVG is still installed, but all its shortcuts have been removed. Given the issues I’ve had with 3rd party AV and Windows 8+ build updates, this may be the new normal for Windows. If that’s the case, hopefully that means MS is going back to making Windows Defender a best-in-class security solution.

I updated to Windows 10 Technical Preview Build 9860 Action Center earlier and immediately ran into Windows Action Center telling me that my PC wasn’t protected and that I should turn antivirus and spyware protection on. Since I run AVG Antivirus FREE 2015 on it, I shouldn’t have seen that message.

Clicking Action Center’s own enabling options didn’t help.* AVG Antivirus FREE 2015 was showing that its Computer and Identity shields were down, which invoking its UI’s proffered single click solution did nothing to change.

Figuring this might be another case of a service failing to start in Windows 10 TP, I opened Services and found that AVGIDAgent wasn’t running. Trying to start it manually produced a long error. At my wits end, I decided that perhaps AVG and Windows 10 TP were incompatible and so I’d be better off just running Windows Defender. I tried uninstalling AVG, but the uninstall failed due to “insufficient privileges” despite me being on an admin account. Services showed no option for manually stoppingĀ  AVG WatchDog either.

A tale of 2 services. AVG WatchDog can't be manually stopped; AVGIDSAgent can't be manually started.
A tale of 2 services. AVG WatchDog can’t be manually stopped; AVGIDSAgent can’t be manually started.

If you run into this situation, here’s how to fix it:

  1. Download the AVG Remover that matches your OS (e.g. 64-bit for x64) here.
  2. Run AVG Remover, which along with removing AVG dumps 2 extensive log files – avgremover.log and avgremover_msilog.txt – in the folder from which it was launched. Your PC will reboot.**
  3. Download AVG.
  4. Reinstall AVG.

The above steps should clear Action Center’s warnings.

Everything's back to normal!
Everything’s back to normal!

I think a couple things are at work here. The first is that 3rd party antivirus and Windows OS updates don’t work perfectly well with each other. This is disappointing but not surprising, considering that the former has the deepest hooks possible into the latter for a client application but both are separately developed. The second is I suspect a significant under the hood change between Windows 10 TP and previous Windows versions in how client applications invoke services. I base this suspicion on the above complications with along with EMET 5.0 – a Microsoft security product!!! – being unable to start the service necessary to complete its installation without manual user intervention.

The above method also works if Identity protection suddenly stops working and refuses to be enabled.

*This happens occasionally with avast! on Windows 8.1, so it’s not shocking.

**Upon rebooting, you’ll see the same Action Center warnings again. You can try auto-enabling Windows Defender via them, but that didn’t work for me. Neither did trying to manually start Windows Defender’s UI, as the Windows apparently still thought 3rd party antivirus was installed. If this is the case for you too, just proceed to Steps 3 and 4.

How to get past the EMET 5.0 “sufficient privileges” installer error on Windows 10 TP

Manually start the Microsoft EMET Service during installation.

UPDATE: This problem is apparently resolved in EMET 5.1.

When installing EMET 5.0 on Windows 10 Technical Preview x64 using an admin account, the following error message pops up:

Service ‘Microsoft EMET Service’ (EMET_Service) failed to start. Verify that you have sufficient privileges to start system services.

with a Try Again option.

No compatibility setting works, and there’s no Run as administrator option available on right-clicking the .msi file either. Running the .msi via an elevated command prompt also doesn’t fix the issue.

To get around this, upon seeing the error message:

  1. Fire up Services.
  2. In the list of services, find Microsoft EMET Service (EMET_Service).

    Windows Services are great, but they can be finicky.
    Windows Services are great, but they can be finicky.
  3. Click Start the service.
  4. When the service has started, click Try Again on the error message dialog.

The EMET installer should now complete as normal:

EMET 5.0 on Windows 10 TP.
EMET 5.0 on Windows 10 TP.

Thanks pc-learner for this solution.