I recently installed a new Windows 10 Insider Slow Ring build, only to find all my pinned taskbar UWP shortcuts missing. The apps didn’t show up the Start menu either via searching or manual scrolling.
The fix is here and involves a bit of PowerShell wrangling for batch operation, but all you have to do is literally copy and paste commands. I highly recommend you close all UWP apps before doing it, but don’t worry about “resource currently in use” error messages after that as the commands will work just fine.
🎶 If you’re having RAM problems I feel bad for you son 🎶
Ever gotten the error message below?
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:
Open the Start Menu.
In the window that pops up, find RunSWUSB.
Right-click on the above entry.
Click Stop if it isn’t greyed out.
In the window that pops up, under the General tab, click the Startup type: dropdown menu.
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.
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
Click Update & Security.
Click Advanced Options.
Check the Defer feature updates box.
Retry the update process.
That didn’t work, so I tried:
Running the Windows Update Troubleshooter
Open Control Panel.
In the View by: dropdown, select Small icons.
Click Fix problems with Windows Update.
Follow the onscreen instructions to fix any problems that are found.
Retry the update process.
That didn’t work either, so I tried:
Deleting the C:\$WINDOWS.~BT folder
Open File Explorer.
Click the View tab.
Check the Hidden items box in the Show/hide ribbon section.
Navigate to the C:\ drive.
Delete the $WINDOWS.~BT folder.
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
Download the latest Slow Ring ISO here. You’ll need to sign in 1st so the page knows you’re a Windows Insider.
Using WinRAR, 7-Zip, or a similar archive extraction tool, extract the ISO file to a folder.
Open the above folder.
Launch the setup file.
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.
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.)
Disconnect the laptop from the internet (disable Wi-Fi, unplug Ethernet cable.)
Disconnect all non-essential USB peripherals, including mice if you have a working laptop touchpad.
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:
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:
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:
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#.
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.
If you run into this situation, here’s how to fix it:
Download the AVG Remover that matches your OS (e.g. 64-bit for x64) here.
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.**
The above steps should clear Action Center’s warnings.
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.
**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.