Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, December 20, 2016 5:36 PM
Hello,
I am experiencing this random error that occurs on any tool that I right click and choose run as administrator. The first time I do this for a specific RSAT tool I get this error message. For example right now I have a message that says C:\WINDOWS\system32\dsa.msc The stub received bad data. The only option is to click OK and dismiss this message box.
If I dismiss the message box and try the tool again, it works fine. This could be any tool like DHCP, DNS, ADUC, WSUS, heck even a third party console application like Veeam, SolarWinds Patch Manager, you name it, I've seen it.
Any idea what a proper fix will be?
My PC is on Windows 10 Pro 1607 Build 14393.0.
I run it as a regular user account but sometimes need to run an RSAT tool as my specific Domain Administrator account to manage servers and services throughout our company. Remote Server Administration Tools is much more convenient than RDP or open a VMWare console to specific application servers.
All replies (9)
Tuesday, December 20, 2016 5:39 PM
I forgot to mention, I get this error on my laptop as well (Dell XPS15) which is running Windows 10 Pro Version 1607 Build 14393.10. Therefore this error is not specific to a specific machine. I believe I've also seen another admin have this same issue on their Dell Precision Workstation, also running Windows 10 Pro 1607.
Wednesday, December 21, 2016 7:11 AM | 1 vote
Hi,
Please check this office kb2028588
Error 1783: The stub received bad data
https://support.microsoft.com/en-us/kb/2028588
Besides, I suggest to update system to the latest build 14393.576 to test if repair issue.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 21, 2016 7:13 AM | 1 vote
In addition, there is a similar case may give you a hint.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 21, 2016 1:06 PM
kb2028588 Applies to
Microsoft Exchange Server 2003 Service Pack 2, Windows Server 2008 Service Pack 2
In all instances, this message is only ever seen on Windows 10 Pro, 1607.
Regarding the second link you posted, that has to do with one way external trust between domains. There is only one domain involved here. 3 2012 R2 Domain Controllers, and Windows 10 Pro workstation managing them or third party console tools run as a domain administrator (Veeam, SolarWinds Patch Management, etc..)
Wednesday, December 21, 2016 1:53 PM
Here's an example of a third party tool. I right click Solar Winds Patch Management and select run as administrator. Right away it says C:\Program Files\SolarWinds\Patch Manager\Console\MMCLoader.exe The stub received bad data.
I did not even get to my authentication prompt again, so I do not think it even queried any of our 3 DC's at this point. The Windows 10 O/S needs to launch a username and password dialog box for me to enter domain admin level credentials for this tool to work.
I then try it again, and like usual it always works the second time.
Its just a waste of time to search for a tool, right click, run as administrator, dismiss the error, then search for the tool again, right click, run as administrator, provide appropriate credentials and then finally access that tool.
Tuesday, January 3, 2017 5:47 PM
This even happens on local computer tools. For example I was going into device manager so I click to search and type in devmgmt.msc and right click on the search result and choose run as administrator. The first time I do this I get "The stub received bad data". I do it a second time and it properly displays a username and password dialog box, in which I authenticate and then device manger opens.
Tuesday, January 3, 2017 9:37 PM
Do you have Dropbox installed?
Saturday, February 11, 2017 6:34 AM
I'm getting this on Server 2016 Datacenter. Behavior described above is exactly what I'm seeing
Do you have junctions in the user profiles perchance? I'm thinking this may have something to do with my error, but I am unsure.
-g
Monday, March 13, 2017 1:55 PM
For us the article (ID: 2028588) here solved the problem. On the affected OS (a test system) we deleted some unused software from past tests and get rid of the issue.