Getting the error “unexpected error; quitting” in Win10 version 1903? Blame the latest cumulative update

Topic

New Reply

Yet another bug in this month’s first cumulative update for Win10 version 1903, KB 4517389. Our own Mark Busby described the symptoms: After installin
[See the full post at: Getting the error “unexpected error; quitting” in Win10 version 1903? Blame the latest cumulative update]

Reply | Quote

Replies

Since when do 16 bit apps even work on Windows?  Or is this specific to 32 bit builds?

2 users thanked author for this post.

steeviebops, b

Reply | Quote

16 bit apps work on Windows 10, but you have to install 32 bit version. I have several PCs in our company with Windows 10 32 bit, just to run 16 bit program Zebra Bar One. It will last for several years, then it wont be needed anymore. but yes, you can run 16bit apps on Windows 10.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

1 user thanked author for this post.

Paul T

Reply | Quote

Has to be specific to 32-bit; 64-bit has no NTVDM.

1 user thanked author for this post.

doriel

Reply | Quote

Seams a new build 1903/1909 cumulative update, KB4522355, is on the way.
BTW let’s talk about 1909.
Install it, try searching in a folder for something. When typing something in the search edit box in a folder in Windows explorer,
No instant search results anymore? One have to press enter!
Yes, this exists even if you install KB4522355,.
And no, you won’t see it if you clean install 1909 using MSDN ISOs. Heads up. Have a great day/night/whatever…

Reply | Quote

The suggestion while typing requires cataloguing ahead of time. Could this very fresh install have been prevented from cataloguing or not yet had time to build the reference in the background? Will it work better tomorrow without making any change to settings?

Reply | Quote

armond wrote:

BTW let’s talk about 1909.
Install it, try searching in a folder for something. When typing something in the search edit box in a folder in Windows explorer,
No instant search results anymore? One have to press enter!
Yes, this exists even if you install KB4522355,.

I get results every time before pressing enter in File Explorer search box on 1909 with KB4522355.

1 user thanked author for this post.

Reply | Quote

If you please take a look at this pictures?

It shows my issue.

Searching for *.dll in C: drive, for example. with and without 1909 package installed.

Have to press enter after typing *.dll to actually search for it in 1909.

Clear?

Reply | Quote

The way that File Explorer search box works has certainly been changed in version 1909:

File Explorer improvements

What does that mean for you? Once you have the new experience, as you type in File Explorer’s search box, you’ll now see a dropdown populated with suggested files at your fingertips that you can pick from.

These improved results can be launched directly by clicking the entry in the new suggestions box, or if you want to open the file location, just right-click the entry and there’ll be an option to do so. If you need to use commands or dig deeper into non-indexed locations, you can still press enter and populate the view with the traditional search results.

We’ve also updated the design, so now as soon as you click the search box in File Explorer (or press CTRL+E to set focus to it), you’ll see the dropdown list with your search history.

Showing the new dropdown that appears when you type in File Explorer’s search box:

https://blogs.windows.com/windowsexperience/2019/05/08/announcing-windows-10-insider-preview-build-18894/

You may need to build up some search history or turn on search indexing before it functions better.

1 user thanked author for this post.

Reply | Quote

Thanks. Now got the idea!

Don’t like it at all.

I never hated Windows that much! I got use of instant searching in File Explorer since Vista days.

It is just probably a registry tweak or something and should be reversable… Thanks for letting me know.

1 user thanked author for this post.

b

Reply | Quote