Error 1783 the stub received bad data

Hi

I want to launch a process under a local user . The new process need new environment variable .

So I have created a local user . Create Environment Block using the token obtained from LogonUser API. Then added new environment variable to the Environment Block . When CreateProcessWithLogonW is called with this updated Environment Block application throws
error code 1783 ( stub received bad data) .

if I pass IntPtr.Zero for the «pNewEnvironmentBlock » parameter of CreateProcessWithLogonW it works but that is not what I want .

I wanted to pass additional environment variable specific to the new process .

I created a local user with out admin rights and gave password to run this program

please see the code below .

regards

Somaraj

using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.IO;
using System.Runtime.InteropServices;
using System.Text;


namespace UserProcess
{

 class Program
    {
        static void Main(string[] args)
        {
          
            IntPtr processHandle = Logon.Launch(@"C:WindowsSystem32cmd.exe");


        }
    }


    internal class Logon
    {
     
        private const uint TOKEN_QUERY = 0x0008;
        private const uint TOKEN_DUPLICATE = 0x0002;
        private const uint TOKEN_ASSIGN_PRIMARY = 0x0001;
        [Flags]
        private enum LogonFlags
        {
            LOGON_WITH_PROFILE = 0x00000001,
            LOGON_NETCREDENTIALS_ONLY = 0x00000002
        }

        [Flags]
        private enum CreationFlags
        {
            CREATE_SUSPENDED = 0x00000004,
            CREATE_NEW_CONSOLE = 0x00000010,
            CREATE_NEW_PROCESS_GROUP = 0x00000200,
            CREATE_UNICODE_ENVIRONMENT = 0x00000400,
            CREATE_SEPARATE_WOW_VDM = 0x00000800,
            CREATE_DEFAULT_ERROR_MODE = 0x04000000
        }

        [StructLayout(LayoutKind.Sequential)]
        private struct ProcessInfo
        {
            public readonly IntPtr hProcess;
            public readonly IntPtr hThread;
            public readonly uint dwProcessId;
            public readonly uint dwThreadId;
        }

        [StructLayout(LayoutKind.Sequential, CharSet = CharSet.Unicode)]
        private struct StartupInfo
        {
            public int cb;
            public readonly string reserved1;
            public readonly string desktop;
            public string title;
            public readonly uint dwX;
            public readonly uint dwY;
            public readonly uint dwXSize;
            public readonly uint dwYSize;
            public readonly uint dwXCountChars;
            public readonly uint dwYCountChars;
            public readonly uint dwFillAttribute;
            public readonly uint dwFlags;
            public readonly ushort wShowWindow;
            public readonly short reserved2;
            public readonly int reserved3;
            public readonly IntPtr hStdInput;
            public readonly IntPtr hStdOutput;
            public readonly IntPtr hStdError;
        }

        [DllImport("advapi32.dll", CharSet = CharSet.Unicode, ExactSpelling = true, SetLastError = true)]
        private static extern bool CreateProcessWithLogonW(
            string principal,
            string authority,
            string password,
            LogonFlags logonFlags,
            string appName,
            string cmdLine,
            CreationFlags creationFlags,
            IntPtr environmentBlock,
            string currentDirectory,
            ref StartupInfo startupInfo,
            out ProcessInfo processInfo);

        [DllImport("kernel32.dll")]
        private static extern bool CloseHandle(IntPtr h);

        [DllImport("userenv.dll", SetLastError = true, CharSet = CharSet.Unicode)]
        internal static extern bool CreateEnvironmentBlock(ref IntPtr lpEnvironment, IntPtr hToken, bool bInherit);

      [DllImport("advapi32.dll", SetLastError = true, BestFitMapping = false, ThrowOnUnmappableChar = true)]
        [return: MarshalAs(UnmanagedType.Bool)]
        internal static extern bool LogonUser(
            [MarshalAs(UnmanagedType.LPStr)] string pszUserName,
            [MarshalAs(UnmanagedType.LPStr)] string pszDomain,
            [MarshalAs(UnmanagedType.LPStr)] string pszPassword,
            int dwLogonType,
            int dwLogonProvider,
            ref IntPtr phToken);

       
        private static List<string> ReadEnvironmentVariables(IntPtr envBlock)
        {
            var strList = new List<string>();
            while (true)
            {
                var str = Marshal.PtrToStringUni(envBlock);
                if (str.Length == 0)
                {
                    break;
                }
                //yield return str;
                strList.Add(str);
                envBlock = new IntPtr(envBlock.ToInt64() + (str.Length + 1 /* char  */)*sizeof (char));
            }

            return strList;
        }

        
        public static IntPtr Launch(string appCmdLine)
        {
          
            IntPtr token = IntPtr.Zero;

            const int LOGON32_LOGON_INTERACTIVE = 2;
            const int LOGON32_PROVIDER_DEFAULT = 0;

            if (!LogonUser("localuser", "HOSTNAME", "PassWord",
                LOGON32_LOGON_INTERACTIVE, LOGON32_PROVIDER_DEFAULT, ref token))
            {

                Console.WriteLine("Error code: {0}", Marshal.GetLastWin32Error());
            }

          
            var strList = new List<string>();
            var envBlock = IntPtr.Zero;
            if (token != IntPtr.Zero)
            {

                var retVal = CreateEnvironmentBlock(ref envBlock, token, true);
                if (retVal == false)
                {
                    var message = String.Format("CreateEnvironmentBlock Error: {0}", Marshal.GetLastWin32Error());
                    Debug.WriteLine(message);
                }
               
            }


            strList = ReadEnvironmentVariables(envBlock);

            //add new environment vaiable 
            strList.Add("Test="Name"");
            var newEnvironmentBlock = string.Join("", strList.ToArray()) + "" + "" + "" + "";
            var pNewEnvironmentBlock = Marshal.StringToHGlobalUni(newEnvironmentBlock);


            var si = new StartupInfo();
            si.cb = Marshal.SizeOf(typeof (StartupInfo));
            si.title = "This is impersonated command prompt";

            var pi = new ProcessInfo();
            var app = Path.Combine(Environment.SystemDirectory, appCmdLine);

            if (CreateProcessWithLogonW("localuser", "HOSTNAME", "PassWord",
                LogonFlags.LOGON_NETCREDENTIALS_ONLY,
                app, null,
                CreationFlags.CREATE_UNICODE_ENVIRONMENT | CreationFlags.CREATE_NEW_CONSOLE, pNewEnvironmentBlock, @"C:WindowsSystem32",
                ref si, out pi))
            {
                CloseHandle(pi.hProcess);
                CloseHandle(pi.hThread);
            }
            else
            {
                Console.WriteLine("Error code: {0}", Marshal.GetLastWin32Error());
            }

            return pi.hProcess;
        }

       
    }
}

If you are trying to run any program, .bat file, .msi file, or running any kind of windows utility like service manager, device manager, etc. you must have encountered The stub received bad data windows 10 error. Also, when trying to copy, move, rename, and delete files over a network, the error appears. Also, the error occurs when using explorer.exe. Well, in this troubleshooting guide, we will try to eliminate the error; we have collected various methods to fix the issue. But first, let’s go through all the causes of this issue.

Causes of The Stub Received Bad Data Error:

When talking about the causes of The Stub Received Bad Data windows 10 Error. We have come across some cases that have been reported by all the users commonly. If your system files corrupted or maybe there are some of the bad sectors in your physical hard drive, then this error occurs. On the other hand, there might be corruption in the file or folder as well. Also, while installing any application, then also this error appears.

• Corrupted system files
• Bad sectors on the hard drive
• Corrupted application installer
• Recent recovery from virus or malware

Similar Types of The Stub Received Bad Data Error:

• The stub received bad data Palo alto
• Keyring cache token has failed 1783 credwrite The Stub Received Bad Data
• Rpc_x_bad_stub_data
• Sfc /scannow

In order to fix The Stub Received Bad Data windows 10 Error. We have gathered a couple of methods that will help fix the issue. In the first method, we will perform an SFC scan. The second method will be all about DISM. Thirdly we will perform a system update. In the fourth method, we will try to fix the issue by uninstalling the problematic application. Finally, if any of the methods fail to work, we will perform a system reset.

1. Performing an SFC Scan –

In the first method, we try to perform a system file scan to fix The Stub Received Bad Data windows 10 issue. We will use the command prompt to perform the SFC scan. Follow all the commands carefully.

• STEP 1. In the start menu, type cmd and make sure to run as administrator
• STEP 2. In the command prompt execute the following command

sfc /scannow

• STEP 3. The command may take some time to process
• STEP 4. After the command is executed restart your system

2. Performing a DISM Scan –

Now, if you are still getting The Stub Received Bad Data windows 7 error, try to perform a DISM scan. DISM scan will fix the corrupted boot file.

• STEP 1. In the start menu, type cmd and make sure to run as administrator
• STEP 2. In the command prompt execute the following command

DISM /Online /Cleanup-image /Scanhealth  

• STEP 3. After that restore your health by executing the following command

DISM /Online /Cleanup-image /Restorehealth

• STEP 4. Now again start your system to make all the changes effective

3. Updating Windows –

Another way to fix windows The Stub Received Bad Data windows 10 issue is by updating your system. By updating windows, all your driver and system files get updated, resulting in a healthy system. Follow the steps to update your system.

• STEP 1. Click on Start Menu, now click on the Gear button

• STEP 2. In the Settings windows, click on Update & Security

• STEP 3. On THE left of the screen, click on Windows Update link
• STEP 4. Finally, click on Check for updates to scan for any pending updates

• STEP 5. Make sure that you are connected to the internet, and your system will automatically download the update

4. Uninstall Problematic Program –

If you are getting services msc The Stub Received Bad Data windows 7 error after installing a specific program, maybe the issue is with the program. Follow the step to resolve the issue.

• STEP 1. In the start menu, and click on the control panel
• STEP 2. Now go to Programs > Program and Features
• STEP 3. Select the problematic program and on the top click on Uninstall

5. Resetting the Windows –

If any of the above methods fail to work, the only resort to fix The Stub Received Bad Data windows 8 issue is by resetting the windows. Follow the steps to reset windows.

• STEP 1. Click on the start menu click on the power button, once all the option comes up hold shift and click the Restart button
• STEP 2. After the system restarts and a blue screen will appear
• STEP 3. From al of the options, Choose Troubleshoot > Reset this PC

• STEP 4. Here you will get the option whether to keep your files or remove everything

• STEP 6. After that click on the Reset button
• STEP 7. Now perform all the on-screen instruction to reset your system finally

Conclusion:

In the above section, we have tried to cover all the possible methods that can fix The Stub Received Bad Data windows 10 Error. Furthermore, we have also included a piece of brief information regarding the causes and effects of the error on the system.

By following this, The Stub Received Bad Data windows 10 guide, we hope you are able to resolve the issue. For more troubleshooting guides and tips, follow us. Thank you!

Hi All,

Ive been searching most everywhere for a solution to this and created an incident for it which lead nowhere other than some level 1 tech saying it was basically all windows rpc service fault (which was probably in her manuscript, but still completely unhelpful).

Anyway, my problem was this when using application aware backups after we upgraded from v7 to v8:

12/2/2014 5:37:27 PM :: VSSControl: FinishSnapshot failed
Failed to execute VIX command: [RPC function call failed. Function name: [BlobCall].
RPC error:The stub received bad data.
 Code: 1783]. 

When application aware backup was turned off, these machines got backed up just fine.

The usual suspects, restarting vmware tools, checking whether logins where actually assigned after the upgrade, double/triple checking logins, making sure vmware tools where all up to date, rebooting VMs etc etc.. all of them made absolutely no difference.

What did in the end work was deleting the VeeamVssSupport service (sc delete VeeamVssSupport from a prompt with priviledges).

After that everything worked as expected (i didn’t need to reboot the VMs after this change).

We had this happen on 5 or 6 machines post the upgrade, some exchange, some mssql and one AD server, so there doesn’t appear to be a clear pattern.

So heres to hoping this gets picked up by a google bot so you don’t have to waste your time finding a solution.

Regards,
Steffen