How to Resolve an Error in NetWkstaGetInfo (2138)

I am running a multitude of Windows-based virtual machines hosted on a bunch of virtualization products, ranging from Microsoft Virtual PC and Virtual Server (yes, I need those for most of the Microsoft Official Curriculum courses I teach), Microsoft Hyper-V, along with those hosted on VMware products such as ESX and (my personal favorite) Workstation.

In the past year or so I began receiving strange error when booting up some of my virtual machines:

Error in NetWkstaGetInfo (2138)

Sponsored Content

What is “Inside Microsoft Teams”?

“Inside Microsoft Teams” is a webcast series, now in Season 4 for IT pros hosted by Microsoft Product Manager, Stephen Rose. Stephen & his guests comprised of customers, partners, and real-world experts share best practices of planning, deploying, adopting, managing, and securing Teams. You can watch any episode at your convenience, find resources, blogs, reviews of accessories certified for Teams, bonus clips, and information regarding upcoming live broadcasts.

The error came up on some of the virtual machines I used on VMware Workstation, but because after clicking on the “OK” button nothing wrong happened to my machines and I could continue working normally, I never took enough time to investigate the error. This is why I could not pinpoint the exact times when it occurred.

I tried to find a solution for this strange error. I searched Google for the error message but while there were many hits on it, no result seemed to suit my specific environment. Some results did, however, point me to the fact that this error usually appears on VMs running on VMware products.

Another solution I found gave me a hint. It suggested to take a look at the computer’s startup settings by using MSCONFIG, and if that doesn’t help, they suggested repairing the computer’s system files by running SFC SCANNOW. While this command usually repairs the operating system’s system files, I wanted to find something else.

So I moved on, and I wanted to find out exactly what product or software or service or Windows component brought it up. For this I used Microsoft’s (ones – Sysinternals) Process Explorer.

From the product’s site:

Process Explorer shows you information about which handles and DLLs processes have opened or loaded.

The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you’ll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you’ll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.

The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.

Process Explorer:

So I ran Process Explorer. One of the nice things about it, is the fact that you can use a “target” cross and drag it on top of any visible application (or error message in this case), and be pointed to the executable name and information of the process behind the application or error window.

Process Explorer pointed me to the process causing the error. It was in front of my eyes all the time, literally.


I am using Backinfo.exe to display the netbios name of the machine and information about the CPU, memory,OS, IP address, logged on username and more, and you can clearly see it behind the error message on the first screenshot on this article. Backinfo.exe was once available from Microsoft, but the only working link to download it I found was this:


or here:


Please Note: as the files above are NOT provided/hosted this site, or Microsoft, before running the downloaded file(s) on your system, make sure you properly scan them with  decent anti-virus software and use at your own risk!

On the other hand, you can use BGinfo (again, another sysinternals tool):



Related Topics:


Don't have a login but want to join the conversation? Sign up for a Petri Account

Comments (0)

Leave a Reply

External Sharing and Guest User Access in Microsoft 365 and Teams

This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

You will learn:

  • Who should be allowed to be invited as a guest?
  • What type of guests should be able to access files in SharePoint and OneDrive?
  • How should guests be offboarded?
  • How should you determine who has access to sensitive information in your environment?

Sponsored by:

Office 365 Coexistence for Mergers & Acquisitions: Don’t Panic! Make it SimpleLive Webinar on Tuesday, November 16, 2021 @ 1 pm ET

In this session, Microsoft MVPs Steve Goodman and Mike Weaver, and tenant migration expert Rich Dean, will cover the four most common steps toward Office 365 coexistence and explain the simplest route to project success.

  • Directory Sync/GAL Sync – How to prepare for access and awareness
  • Calendar Sharing – How to retrieve a user’s shared calendar, or a room’s free time
  • Email Routing – How to guarantee email is routed to the active mailbox before and after migration
  • Domain Sharing – How to accommodate both original and new SMTP domains at every stage

Aimed at IT Admins, Infrastructure Engineers and Project Managers, this session outlines both technical and project management considerations – giving you a great head start when faced with a tenant migration.the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

Sponsored by: