SCCM: More Windows Setup Log Details

SCCM: More Windows Setup Log Details

The following log files are created when an upgrade is successful:

  • C:\Windows\Panther\Setupact.log
  • C:\Windows\panther\setuperr.log
  • C:\Windows\inf\setupapi.app.log
  • C:\Windows\inf\setupapi.dev.log
  • C:\Windows\panther\PreGatherPnPList.log
  • C:\Windows\panther\PostApplyPnPList.log
  • C:\Windows\panther\miglog.xml

The following log files are created when an upgrade fails during installation before the computer restarts for the second time:

  • C:\$Windows.~BT\Sources\panther\setupact.log
  • C:\$Windows.~BT\Sources\panther\miglog.xml
  • C:\Windows\setupapi.log
  • [Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log

The following log files are created when an upgrade fails during installation after the computer restarts for the second time:

  • C:\Windows\panther\setupact.log
  • C:\Windows\panther\miglog.xml
  • C:\Windows\inf\setupapi.app.log
  • C:\Windows\inf\setupapi.dev.log
  • C:\Windows\panther\PreGatherPnPList.log
  • C:\Windows\panther\PostApplyPnPList.log
  • C:\Windows\memory.dmp

The following log files are created when an upgrade fails, and then you restore the desktop:

  • C:\$Windows.~BT\Sources\panther\setupact.log
  • C:\$Windows.~BT\Sources\panther\miglog.xml
  • C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log
  • C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log
  • C:\Windows\memory.dmp

The following log files are created when an upgrade fails, and the installation rollback is initiated:

  • C:\$Windows.~BT\Sources\Rollback\setupact.log
  • C:\$Windows.~BT\Sources\Rollback\setupact.err
Advertisements
SCCM: Windows Setup Log File Locations

SCCM: Windows Setup Log File Locations

The below table shows you where the log files are stored during Windows Setup handy just for reference

Log file location Description
$windows.~bt\Sources\Panther Log location before Setup can access the drive.
$windows.~bt\Sources\Rollback Log location when Setup rolls back in the event of a fatal error.
%WINDIR%\Panther Log location of Setup actions after disk configuration.
%WINDIR%\Inf\Setupapi.log Used to log Plug and Play device installations.
%WINDIR%\Memory.dmp Location of memory dump from bug checks.
%WINDIR%\Minidump.dmp Location of log minidumps from bug checks.
%WINDIR%\System32\Sysprep\Panther Location of Sysprep logs.
SCCM: TS Fails with code 80004005

SCCM: TS Fails with code 80004005

Hi Guys

Today we have been presented with the following error 0x80004005 during a deployment of Windows 10 in a PXE environment after some digging around the logs we saw the following line

Failed to locate the local data path. The files needed to resume the task sequence are missing

so ultimately the DP that you are deploying from does not have the required packages to complete the task sequence. To resolve re-distribute your content to the selected DP and the issue should go away.

Also you can check the references tab to see if all the content is available and compliant as per the deployment on the Task Sequence you are attempting to execute

News: New Features in Power BI

News: New Features in Power BI

The December 2018 release of PowerBI from Microsoft has tones of new feature updates take a look at this list below

Reporting

Analytics

Modeling

Custom visuals

Data connectivity

Data preparation

Other

 

SCCM: TS Fails with code 80070070

SCCM: TS Fails with code 80070070

Today we have encountered the error 0x80070070 this ultimately means that there is not enough free space on the destination disk. To resolve this issue follow the below steps

  • Press [F8]
  • Open the command line tool DiskPart by issuing the following command
    • “DiskPart”
  • List the attached disks and take a look at the free space column to verify this is the issue
    • “List Disk”
  • Then select the disk that you wish to clear down
    • “Select Disk <X>”
      • Replace “<X>” with the disk number as show in the list disk command
  • Then list the volumes
    • “List Volume”
  • Then delete your volumes
    • “Delete Volume <X> Override”
      • Replace “<X>” with the volume number as listed in the command List Volume
  • Your disk has now been wiped and now re-attempt to run the Task Sequence

Running the above command’s will resort to data loss please backup if required