QFE Number mismatch

I keep getting Failover Cluster Validations failures and can't seem to figure out what the issue is.  Thank you for your asistance.  Here are the details.  (2) Server 2012 R2 Data Center with (1) MSA 2040 Direct Fiber with 10GB iSCSI Card.  The "Validate Microsoft MPIO-based disks" are failing with this error.

Node 1
Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
Microsoft DSM 6 3 9600 17401

Getting information about registered device-specific modules (DSMs) from node 2

Node 2
Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
Microsoft DSM 6 3 9600 0

For the device-specific module (DSM) named Microsoft DSM, versions do not match between node 1 and node 2
For the device-specific module (DSM) named Microsoft DSM, versions do not match between node 2 and node 1

The only thing I see different is the QFE number but I cant seem to figure out why.  the mpclaim shows them as both using Microsoft DSM.
iTeam HelpDeskAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Microsoft-provided in-box providers can be updated via windows update. 6.3.9600 was RTM. One of your nodes has an updated patch and the other is still at RTM. Windows update is your friend here.
iTeam HelpDeskAuthor Commented:
I have updated everything on both servers already and they both are on 6.3.96 Build 9600.  This did not resolve the issue.
Cliff GaliherCommented:
17041 isn't RTM. As I recall, that was the May 2014 refresh. Make sure that is installed. Check the update list specifically. Precedence or 3rd party patch management (such as WSUS) can cause an update to not appear, but another node build from refreshed media or built in a NOC before deployment can have different patches.
iTeam HelpDeskAuthor Commented:
So I figured out what happened.  When I found that my updates were legit and there were no more available updates from microsoft, I decided to uninstall MPIO and Reinstall and I ran into an issue where I couldn't uninstall it.  So I researched the issue and this is what I found.  Reinstalled MPIO and this resolved the original issue on this question.  So all I can guess is that it was a faulty install on Node 2 for the MPIO.  I don't use 3rd party patch management as this time since this was a new server and had not setup any yet.  All my updates were direct from Microsoft.  Here is the solution I found that resolved the issue.  This was exactly the issue that I was experiencing with my QFE being "0"

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
iTeam HelpDeskAuthor Commented:
I am accepting my own answer becuase the issue was a faulty MPIO install which could only be repaired by a registry fix so I could reinstall the MPIO.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.