Bablosoft

Locked out of Windows because of BAS

Support
  • A

    Sorry if this might be a noob problem, but here it is: tried running BAS on my laptop (Windows 11) and I am locked out every time Windows locks (PIN and password are not working, Windows said the user has been temporarily locked out). The user is Administrator and I'm starting BAS as administrator (Run as administrator)

    In Event Viewer > Windows Logs > Security I'm constantly seeing this error (audit failure):

    An account failed to log on.

Subject:
	Security ID:		DESKTOP-\ZZZZZ
	Account Name:		ZZZZZ
	Account Domain:		DESKTOP-
	Logon ID:		0xB3DB5

Logon Type:			2

Account For Which Logon Failed:
	Security ID:		NULL SID
	Account Name:		ZZZZZ
	Account Domain:		DESKTOP-

Failure Information:
	Failure Reason:		Unknown user name or bad password.
	Status:			0xC000006D
	Sub Status:		0xC000006A

Process Information:
	Caller Process ID:	0x42bc
	Caller Process Name:	**C:\Users\ZZZZZ\AppData\Roaming\BrowserAutomationStudio\apps\31.0.0\Worker.1\chrome\worker.exe**

Network Information:
	Workstation Name:	DESKTOP-
	Source Network Address:	-
	Source Port:		-

Detailed Authentication Information:
	Logon Process:		Advapi  
	Authentication Package:	Negotiate
	Transited Services:	-
	Package Name (NTLM only):	-
	Key Length:		0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
	- Transited services indicate which intermediate services have participated in this logon request.
	- Package name indicates which sub-protocol was used among the NTLM protocols.
	- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

    I've added C:\Users\ZZZZZ\AppData\Roaming\BrowserAutomationStudio\apps\31.0.0\Worker.1\chrome\worker.exe as an allowed app in Windows Defender but it doesn't help.

    I'm also running BAS on 5 other VPS machines, connecting them through Remote Desktop, I'm seeing the same type of Audit Failures there too, but it looks like those machines are not affected (Windows Server 2016)

    Any ideas?

    0