odourboy

Arg! KB4043961 Has Trashed my Sim.. Help!

39 posts in this topic

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?

0

Share this post


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

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.

0

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.

0

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.

0

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!

0

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.

0

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:

 

0

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