Windows Search using cortana closes 2 seconds after typing a single character and no result are displayed

Question

I can type one letter in the search field and then am prevented from typing more. Then cortana closes:

I tried running the windows index troubleshooter, and no problems were found. I tried running sfc /scannow. I tried deleting this key described by this post which didn't work:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion‌​\Explorer\FolderType‌​s\{ef87b4cb-f2ce-478‌​5-8658-4ca6c63e38c6}‌​\TopViews\{00000000-‌​0000-0000-0000-00000‌​0000000}

After creating a new account, cortana works but I want to keep the original account.

While trying to follow this thread: When I stop the service named WSearch, briefly I can use cortana again but the service restarts itself after about ten seconds so I can't run the command marked at code segment 3 below suggested by the post to do while the service is closed and I don't know how to disable it. I'm running Windows 10 home and GPedit.msc is not available. Ignoring disabling WSearch and running the similar commands to reinstall windows store suggested above and here produce errors saying a higher version of the package is already installed.
1:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

2:

Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

3:

$manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest

Answer 1

For me the following post solved the problem:

make a backup of HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search in the registry and then delete the whole entry.

(found here: https://www.tenforums.com/general-support/83709-start-menu-crashing-after-typing-few-letters.html#post1561835)

Answer 2

The upgrade released or made available to me today (Windows 10 home creators edition) version 1703 build 15073.138 fixed the problem for me. Whether it was a corrupted file (likely since the other user account worked) or a bug, maybe will never known.