60008 errors but not on ALL pushes

The Toolkit General Discussion
1

Using 3.10.0. We have a push using Symantec Management Console that fails with 60008. This is on ALL PSADT pushes.
The logs stop at:
<![LOG[[Initialization] :: Current process is running with user account [NT AUTHORITY\SYSTEM] under logged in user session for [<USER>]. This is the OOBE section of AppDeployToolkitMain.ps1. Line 16962.
All computers are W11 64bit
Ideas?

2

v3.10.0 did not last long

you should at least try v3.10.2

3

Updated 3.10.2 Same issue. Although it is not many, but we have 140 machines with this problem

4

If that is the last thing that gets logged the problem is probably in the OOBE / ESP check that comes next in the script. An idea is to add some additional logging (temporarily) for that part to verify exactly where in that code it fails. I would have added it before/after:
Add-Type -TypeDefinition $TypeDef -Language CSharp
to begin with.

5

REM’d out the calling OOBE check and the install did not hang and was successful.
So the question is why running this csharp code hang all of the PSADT installs?

    $TypeDef = @"
using System;
using System.Text;
using System.Collections.Generic;
using System.Runtime.InteropServices;

namespace Api
{
 public class Kernel32
 {
   [DllImport("kernel32.dll", CharSet = CharSet.Auto, SetLastError = true)]
   public static extern int OOBEComplete(ref int bIsOOBEComplete);
 }
}
"@
    Add-Type -TypeDefinition $TypeDef -Language CSharp

    $IsOOBEComplete = $false
    $hr = [Api.Kernel32]::OOBEComplete([ref] $IsOOBEComplete)
6

You might have differences in your security settings on your computers, so you could look into that by comparing settings.

1 Like
7

Try…Catch return Type: OOBE Error [System.Exception]

1 Like
8

Full error:
OOBE Error [System.Exception] Message: (0) : Warning as Error: Invalid search path ‘C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\include’ specified in ‘LIB environment variable’ – 'The system cannot find the path specified. ’

(1) : using System;

Looks like something I can work with

9

This has to do with whether or not the script has the ability to run interactively. With SCCM, there is an option on the deployment type to allow the script to interact with a user session. That fixes this issue. I would look for something similar with symantec.

10

FOUND the culprit:
Visual Studio installations create an environment variable called LIB. When the version changes the paths change but the environment variable does not.
To duplicate: create a fictitious environment variable called LIB and PSADT will hang
For now, I am adding Try…Catch on the cSharp call in AppDeployToolkitMain.ps1

3 Likes
11

I’ve found that this OOBE check doesn’t work on Windows 7, presumably because the kernel function it calls doesn’t exist or worked differently 15 years ago. Shame this wasn’t tested before incorporating it into the template.

Based on this and the issue above, I suggest commenting-out / removing this logic from AppDeployToolkitMain.ps1. It seems to target a very specific scenario that you can avoid by other means.

1 Like