Can't open start menu or search on build 10061

Question

This seems to happen after each build update, and it is usually fixed by the app-cache repair
Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}
However that isn't working this time.
In event viewer I'm seeing these type of errors appear each time I try to open the start menu
"Activation of app Microsoft.Cortana_8wekyb3d8bbwe!CortanaUI failed with error: The operation was blocked by parental controls. See the Microsoft-Windows-TWinUI/Operational log for additional information."
and
"Unable to start a DCOM Server: CortanaUI as Unavailable/Unavailable. The error: "346" Happened while starting this command:
"C:\Program Files\WindowsApps\Microsoft.Cortana_1.4.3.156_x64__8wekyb3d8bbwe\SearchUI.exe" -ServerName:CortanaUI.AppXwbw90g5vtrwjvhq9gjet3rhd0cy7ctte.mca"
I do use family safety, however the account I am logged on with is a local admin and is a parent account that is not monitored by family safety.
Another example, if I try to launch the Spartan browser, it flashes up briefly then closes. The TwinUI/Operational log give the "blocked by parental controls" error, followed by an Informational entry saying
"Activation of app Microsoft.Windows.Spartan_cw5n1h2txyewy!Microsoft.Spartan.Spartan attempted. Execution state: Attempted activation of the app, 7, The operation completed successfully.."
Any thoughts or suggestions?

Answer 1

Unfortunately, this happens in spells when someone has never used family safety. Nuking from space (refreshing PC) is not the answer I'm seeking, that's for sure. I bet this one will be patched, or just made obsolete, by the expected new build around mid-week.
Update: In my case, which is the non-parental-control-caused version of this, it sure looks like it's tied to RAM usage, explaining the seeming randomness of it for me. Through trial and error, I've found that when hitting RAM usage
slightly higher than 70% (according to Task Manager's figure), the flakiness begins with all things Metro (Start itself, any Metro apps within Start, even the functionality of the clock on the tray) disappear about 1 second after being clicked. So, the workaround
for now is to keep RAM usage down. Due to RAM leakage over time, this means rebooting more than you otherwise might want.
Update 2: I think it's at least exacerbated by, if not caused by, not having a dedicated graphics card on the above system, which uses only Intel's onboard HD Graphics 3000. I say this because on a basically identical system--which in terms
of hardware is only different by the addition of a 1GB AMD graphics card--I'm unable to reproduce the problem.  Both systems are Core i5-2500 with 8GB RAM.