For auditing purposes you will need to report on the updates install on a server and the install status. 

Below is a  powershell script that does just that

 

[email protected]('Unk','Installation','Uninstallation','Other')
[email protected]('Unk','In Progress','Succeeded','Succeeded With Errors','Failed','Aborted')

$updateSession=New-Object -ComObject Microsoft.Update.Session
$updateSearcher=$updateSession.CreateUpdateSearcher() 
$historyCount=$updateSearcher.GetTotalHistoryCount() 
$updateSearcher.QueryHistory(0, $historyCount) | 
    Select-Object Date,
                @{N='Operation';E={$operation[$_.operation]}},
                @{N='Status';E={$resultCode[$_.resultcode]}},
                Title |
    Format-Table -AutoSize
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Exception error highlighted in red:

2020-04-17T00:15:01.297Z cpu3:6375497)@BlueScreen: #PF Exception 14 in world 6375497:vmnic0-0-tx IP 0x41800f027133 addr 0x2

 

Just prior to crash:

2020-04-17T00:14:37.248Z cpu8:2097623)igbn: igbn_CheckTxHang:1699: vmnic0: false hang detected on TX queue 0

2020-04-17T00:14:37.268Z cpu8:2097623)igbn: igbn_CheckRxHang:1557: vmnic0: false hang detected on RX queue 0

2020-04-17T00:15:01.138Z cpu4:2097232)igbn: indrv_UplinkReset:1535: indrv_UplinkReset : vmnic0 device reset started

2020-04-17T00:15:01.224Z cpu5:2097625)igbn: igbn_CheckLink:1316: Link went down for device 0x43073a472540

Vmware KB:

https://kb.vmware.com/s/article/67686

The PSOD is because of a race between reset and data path. There are two issues here:

Tx queue xmit and completion path ran into a race

The above race caused queue stuck and uplink reset, which ran into the PSOD.

Identified thanks to these legends in the vmware reddit:

https://www.reddit.com/r/vmware/comments/dan3k3/pf_exception_14_in_world_2481950vmnic00tx_ip/

 

Fixed in later driver release:

Bug Fixes:

———-

– Fixed intermittent TX hang due to race condition between start and stop of TX queue.

– Fixed duplicate nic reset due to race condition between uplink reset and watchdog threads.

https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI67-INTEL-IGBN-1410&productId=742&download=true&fileId=6296e75493aba08fa77bd2451e8ab50f&secureParam=b4190fca752c9b3ece5c3bee9c6c90c9&uuId=4c01b35e-49d0-47eb-a1d3-778ebd60b045&downloadType=

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

I tried flashing my phone and on reboot it go stuck in a reboot loop with the below

Orange State Your device has been unlocked and can’t be trusted. Your device will boot in 5 seconds

Both the main boot and recovery roms could not be botted into.

Download the latest Boot Room from Leagoo Website

LEAGOO_P1 Pro_OS3.0 Lite_NFP_16_20180317.rar

Download Smart Phone Flash Tool , Enter the Scatter.txt form the rar and put in Download mode

Plug the phone in and it will redownload this

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
  1. Download this on the phone : https://magiskmanager.com/
  2. Obtain your Phones most up-t0-date boot rom online ( e.g. boot.img ) 
  3. Copy this file to the phone
  4. Open up Magisk and choose install and Patch File Option
  5. Find the boot.img you just copied to the phone , once done it should create magisk_patched.img
  6. Copy magisk_patched.img back to the computer 
  7. Download https://www.getdroidpro.com/download-the-latest-adb-fastboot-android-sdk-platform-tools/ on your computer and navigate to directory, copy magisk_patched.img here 
  8. Put the phone into USB Debugging model – Go to About Phone, tap on the build number and tap 5 times  , Go back to setting and go to Developer Mode
  9. Accept the RSA key on the phone and trust 
  10. Navigate to the folder from step 7 in Command Prompt ( CMD )
  11. Enter “adb devices” to make sure the phone appaears
  12. Enter “adb reboot bootloader” to reboot the phone 
  13. Once booted enter “fastboot flash boot magisk_patched.img”
  14. One complete enter “fastboot reboot”
  15. Done
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
  1. Setup an Azure subscription if you haven’t got this already, this will be used for Billing. The storage is under a 1$/Month for 1 GB space 
  2. Create a Storage Container in the right Azure Region with the correct redundancy ( Local Redundancy Storage in Cheaper ) . Use General Purpose V2!
  3. Create a Blob Container in this Storage Resource
  4. Use Storage Explorer to upload files here

  5. Upload what file you would like to deploy
  6. Right click on the file and choose “Get Shared Access Signatue”

I set a 100 Year Expiry , and leave access as Read Only

It will give you URI and query string

Copy the URI ONLY up to the file name ( nothing after e.g. the example below )  and put in $BlobUri

Copy the FULL Query String and put in $Sas

Change the Output Path which will need to exist with a trailing \, this example I have used the Users Desktop

#Variables ( Use the Azure Storage Explorer to get the URI ( Shared Access Signature ) of the file and copy the first part up to the file name in BlobURI and the Query String to the Sas) 
#You will need a new Sas for each file

$BlobUri = 'https://xxxxx.blob.core.windows.net/xxxxx/1.jpg'
$Sas = '?sp=XXXXXXXXXXXXXXXXXXXXXXXXXXXX'
#Output Path with \ on the end
$OutputPath = 'C:\Users\' + $env:UserName + '\Desktop\'



#Gets full Uri
$FullUri = "$BlobUri$Sas"
#Downloads file to outpath with correct file type and file found in BlobURI
(New-Object System.Net.WebClient).DownloadFile($FullUri, $OutputPath + ($BlobUri -split '/')[-1])

Deploy this powershell file via Device Config Scripts

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)