odourboy

Arg! KB4043961 Has Trashed my Sim.. Help!

Recommended Posts

18 hours ago, abschwartzjr said:

Well that is fine and dandy.  But what if your version of Windows 10 does not have the option to revert back as mine doesn't?  Windows 10 Home.

I have Windows 10 Home. Currently, I have the option to 'Uninstall' (not 'Recover') in the left hand column when I select the offending update. It is my understanding that this option will expire after a month, after which the files necessary to go back are deleted by windows. I'm sure I don't have the whole story here and I don't know if the Pro version retains images required to uninstall updates for an indefinite period. Note also that Microsoft can designate an update as uninstallable so you won't be offered the option no matter what.

If, for some reason, you don't have this option you may still be able to uninstall a specific update from the command prompt. I do not know if this works for Windows 10 home or not. This page describes that method (method 3):

https://www.tenforums.com/tutorials/5486-uninstall-windows-update-windows-10-a.html

I also found this post on the answers.microsoft site which claims to allow you to unlock updates that Microsoft has decided should be designated as uninstallable. Sounds risky and I certainly haven't tried it, but here you go:

This site shows how to make Updates uninstallable (but warns it might corrupt the installation of future updates).

This is the english version of the site:
http://borncity.com/win/2016/10/21/windows-updates-fehlende-deinstallation-erzwingen/

SUMMARY:

In the C:\Windows\servicing\Packages directory, find all .MUM files for the KB you want to uninstall.

Change permanence="permanent" to permanence="removable" in all of these files, then it will be uninstallable.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

20 hours ago, Jim Young said:

The best way to go back to a previous version is to go to Windows Update screen, look on the left column and click on Recover.  This will allow you to revert to a previous version.  Microsoft has a couple of questions first before they do it but they do it because you are the boss... the King of your computer.  I know of no way in the Add/Remove Program (unless you know the specific KB).  I upgraded to the latest and greatest Windows a couple of weeks ago and saw issues (not sure if it was Windows 10 or P3DV4.1) and clicked on the Recover button and they reverted me back to my previous version and all is well again.  My P3DV4.1 is now in the most stable condition I have ever had any sim so I might try to update again just to see if it really is Windows 10 at fault.  I do have some minor stuttering with FTX SoCal installed but it is really minor.  I had some StackHash and kernelbase.dll errors after first using P3DV4.1 but I found the solution and I will never ever get another crash.

If you remove an update as you've described, where does that leave you with respect to future updates that might rely on the one you've removed and/or re-applying the one you removed at a later date?

Share this post


Link to post
Share on other sites
3 minutes ago, odourboy said:

If you remove an update as you've described, where does that leave you with respect to future updates that might rely on the one you've removed and/or re-applying the one you removed at a later date?

All I'm saying is that the Recover option is another option that I found works well as it updated me to the latest version of Windows 10 - 1709 (currently have 1703).  It took me from 1709 back to 1703.  Windows Update will try again to install it but, if it does and I see issues that I cannot fix, then I will move back to the earlier version.

Share this post


Link to post
Share on other sites

Just an FYI, since it's Wednesday Nov 15th, 2017, I went ahead and re-enabled all my Win10 updates all the way thru to 1709 and then more after 1709 to get myself current on updates.  

Tested:

1.  Visual Studio - all good, no more CTD when accessing a xaml or aspx file
2.  P3D V4.x - all good now (DX shader compiler seems fixed now, note this does NOT impact OpenGL apps like XP11 since issue was DX only)
3.  Adobe PP 2017 doesn't CTD any more all good

So, it looks like Microsoft held good to their promise for a "fix for the fix" with patch Tuesday Nov 14th updates.

I would still recommend you Create a Restore point prior to the doing the updates.  Important that also disable any AntiVirus software (leave Windows Defender running as it doesn't seem to interfer), and any other software you might have running (check your SysTray and quit as many items there as you can).  Also be aware the updates (even on a fast PC with high ISP bandwidth) took approximately 2.5 hours to complete in my case (keeping in mind I had to run older updates before I got to 1709 and then more updates after 1709) ... so give yourself some free time to get this done.

Cheers, Rob.

Share this post


Link to post
Share on other sites

Hello All,

Just an update for people lost like me.

Microsoft told P3D that the patch from yesterday was only for those who had the Windows 10 1703 installed and NOT the 1709.

I don't understand why they didn't release both of them together in one update but hey! So probably we wait another month (or less I hope!) to fix this.

Meanwhile can some of you with FSX SE edition write to Dovetail games as they need to work with Microsoft about this issue.  Here is the link we need them to know. I've sent many already http://dovetailgames.kayako.com/

Share this post


Link to post
Share on other sites

Thanks for the update guys!

Rob, does the DX Shader compiler fix mean I should delete my Shaders folder in P3D after the update or is this fix referring to something else?

Share this post


Link to post
Share on other sites
48 minutes ago, odourboy said:

Rob, does the DX Shader compiler fix mean I should delete my Shaders folder in P3D after the update

I did, and I would recommend it as it does no harm, just means you have a slight one time delay as the view gets rendered on next entry to P3D flight session.  Also recommend the full 360 (2X slowly) rotation for both VC and outside view.

Cheers, Rob.

Share this post


Link to post
Share on other sites

Oh one VERY important note I should add for 1709 updates ... if you have a Samsung NVMe M.2 and an Asus Motherboard with X299 make sure you update your BIOS to the latest version (Asus BIOS).  

There is a very long thread (several threads) of users having issues with Win 10 1709 update that have NVMe devices ... resulting in a BSOD when attempting to update to 1709, picture taken from someone else having the issue:

https://social.technet.microsoft.com/Forums/getfile/1098520

I ran into this issue and updated from 0702 to 0802 BIOS rev and that resolved the issue.  So if you have an NVMe as your OS boot device, you may run into issues and will need to work with your vendor or in my cases ASUS BIOS update.

Cheers, Rob.

Share this post


Link to post
Share on other sites

Another quick update. 

1709 installed fine on 3 of my PCs, but 1 PC just refuses to install 1709 update.  This error indicates some time of driver issue but no reference of what driver so it's fairly useless error message (note this error was reported using Win10 Update Assistant tool (the standard Windows Update process produces a different error but I suspect related to the same issue).

Win10_1709_InstallError.jpg.5e69e1957117df57a23768963972264b.jpg

Most likely my one non-updateble PC will require a wipe and clean install from a boot USB with Win10 1709 build.

But I guess 3 out 4 PC's updating is about standard for the Microsoft 75% mark.  I'm not entirely sure this issue is related exclusive to NVMe M.2's as all 4 of my PC's have boot NVMe M.2's installed.  Fortunately there are many users with this issue so I'm hoping Microsoft will address this.

FYI, BIOS updates didn't resolve this, all of my PCs are running the latest BIOS versions.

Cheers, Rob.

Share this post


Link to post
Share on other sites
12 minutes ago, Rob Ainscough said:

I'm not entirely sure this issue is related exclusive to NVMe M.2's as all 4 of my PC's have boot NVMe M.2's installed.

I have an Samsung M2 SSD installed and used as the boot drive and updated to Windows 10 1709 successfully.  Have flown several flights in v4.1 and no issues whatsoever.  In fact things appear to be running better than ever before!  I checked and my Samsung NVMe M2 is up-to-date.  If you just installed Windows 10, then run a driver update program like Driver Booster to make sure the SATA controllers and USB ports and sys bus drivers are all up-to-date.  I can guarantee there is no problem associated with Windows 10 and NVMe M2 drives.  It has to be something else conflicting with 1709.  In fact, my Driver Booster program has been finding updates suddenly.  One is the Creative sound card controller.  Hope you can find a fix!

Share this post


Link to post
Share on other sites

Hi Jim,

Agree, 3 out of my 4 PCs all with NVMe M.2s updated, just the one PC didn't, so I tend to agree it may not be a NVMe issue and something else ... just wish Microsoft provided more useful error messages ... I looked up the error code and there was NOTHING useful to be gained other than anything that starts with Hex C1900101 is a driver issue.

Checked that all my drivers are up to date ... just wish Microsoft would provide more info to go on because there are 100's of drivers installed in any given system.

For now, I've just disabled Windows updates, run my own anti-virus/malware software ... I'll keep an eye on this issue to see if Microsoft acknowledge and have a fix within the next couple of months.  If it looks like this is just going to be ignored by Microsoft, then when I have some free time I'll just do a wipe and re-install to "solve" the update problem ... I'm in no rush as the one PC that didn't update is working just fine.

Cheers, Rob.

Share this post


Link to post
Share on other sites

Anyone who still has the "child window" problem after the 1709 update may be interested in this post from Jim Young, who traced the problem on his system to Orbx:

 

Share this post


Link to post
Share on other sites

As of today, does anyone know if all these 'win10 updates vs FSX addon' issues been resolved?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now