FBIde Windows 10 creaters update

[Ache]

Everything was working without a problem.
After the Windows 10 creators update from yesterday (2017-04-11), FBIde is giving a error (0xc0000124).
I've tried several things, including running it in compatable mode.
So far I haven't found a solution to get it working again.

If anyone has a (possible) solution, it sure is welcome.

[deltarho[1859]]

It is working for me, Ache, on Windows 10 ( Version 1703) Pro 64 bit.

Unfortunately 0xc0000124 is a bit like 0xc0000005 in that there are many situations which throw up these errors.

It may have nothing to do with the latest Windows update. Remove your copy of FBIde and download another. If that solves the problem then run Chkdsk. If it does not then at least we have eliminated one suspect.

[Ache]

Windows 10 home, 64 bit
version 1703
build 15063.138

I created a image of the drive before installing the creators update.
If I place that back, everything is working.
As soon as I install the creators update the problem is there again.

Removing FBIde, cleaning up the system (files/folders/registry entries) and installing FBIde again does not solve things.
chkdsk, sfc and other checks/tests don't show any problem. (not even a real small one).

To check if the downloaded version is not the problem I copied it to another system (Windows XP SP3) and tried it there.
Everything is working fine on that system.

I created a backup of the registry of working system (Windows 10), installed the creators update, placed that backup on it.
Doesn't solve the problem either, so it seems it is not a registry problem.

I'll keep testing to see if I can find the culprit.

[Ache]

Windows 10 home, 64 bit
version 1703
build 15063.138

I created a image of the drive before installing the creators update.
If I place that back, everything is working.
As soon as I install the creators update the problem is there again.

Removing FBIde, cleaning up the system (files/folders/registry entries) and installing FBIde again does not solve things.
chkdsk, sfc and other checks/tests don't show any problem. (not even a real small one).

To check if the downloaded version is not the problem I copied it to another system (Windows XP SP3) and tried it there.
Everything is working fine on that system.

I created a backup of the registry of working system (Windows 10), installed the creators update, placed that backup on it.
Doesn't solve the problem either, so it seems it is not a registry problem.

I'll keep testing to see if I can find the culprit.

[fxm]

Have you tested older releases of FBIde 0.4.6r4:
- FBIde 0.4.6r3
- FBIde 0.4.6r2
- FBIde 0.4.6
(at http://fbide.freebasic.net/download)

[deltarho[1859]]

Very strange.

Try this: Fix Windows Update errors

I didn't think that I had a problem but ran the 'Windows Update Troubleshooter' anyway and was told that service registration was missing or corrupt and it was now fixed.

[Ache]

Version 0.4.6

After a few reboots, it suddenly is working again.
I have to guess here, but it looks like something(s) from the creators update needs several reboots to completely finish.

Really strange.

[deltarho[1859]]

Ah, the old "If all else fails give it a resounding blow" solution. I had forgotten about that one. <laugh>

It may have changed but I am reminded of a British Standard Institution guide for mixing concrete and in the instructions was "Thoroughly mix twice".

[fxm]

Me, when I update Windows, I systematically do a double reboot:
- a first for Windows update installation,
- and a second one for me (to check that everything restarts normally after installation).

[Ache]

After a update, Windows need to be shaken, not stirred :-)

[deltarho[1859]]

- a first ...
- and a second ...

Standard Federation practice. The Cardassians, on the other hand, would reboot three times. Same with system backups: Cardassians keep three, the Federation keep two. A Trekky? Nah, I hardly ever watched it. <cough>