Thanks for that link. I’ll peruse it as well. At least Fog is old faithful and got my test computer up and running when USB/DVD both failed me miserably!

Seems legit. May have to try that out.

@tom-elliott Cool. Thanks Tom!

@cml Better mark this as solved. Loved it!

Start-Transcript -Path C:\$([Environment]::Is64BitProcess).txt "Is 64?" [Environment]::Is64BitProcess $pwd if ([Environment]::Is64BitProcess) { $a = Get-BitLockerVolume -MountPoint C: $a | Out-File C:\file.txt -append } else { $arguments = "-ExecutionPolicy Bypass -NoProfile -File temp.ps1 " start-process C:\WINDOWS\sysnative\WindowsPowerShell\v1.0\powershell.exe -ArgumentList $arguments -Wait -WorkingDirectory $pwd }

I know its not pretty, but its a proof of running 64 powershell. In essence, I need the 32bit to launch a 64bit version of powershell. Can’t just run powershell.exe because it goes still into x86.

@Tom-Elliott Okie-tay! Closing ticket, marking solved. Thanks Tom!

@szeraax Thanks for the update. It’s definitely an issue that we will be seeing more and more in the next month.

Not because it is solved, but because I will just have to wait for a magical time in the future when FOG has support for booting NVMe hard drives decently.

Unfortunately those things rarely solve themselves magically. People have to work on it. In this case having the hardware at hand seems to be very crucial as your findings reveal (same zbook model showing different behavior). By the way, have you checked firmware versions?
So what I am trying to say is that it might need your work on testing these things on your devices to hopefully figure things out. But on the other hand I do understand that you/we don’t have the time and expertise to dig through this.

Maybe try going back to using rEFInd plus adding the clover NVMe driver? As I understand it you should be able to add that driver by simply creating a directory drivers_x64 (EFI/boot/drivers_x64) and putting that clover driver EFI file there. rEFInd should scan that directory and load the driver.

Not sure if we’d mark this solved.

@wayne-workman Everything still seems fine for this. Still can’t figure out how to mark as solved, but someone should do that if they can.

So it looks like the API works great for what I need. But how do I mark as solved? I can’t find anything that lets me change this status 😞

My code from the api is something similar to:

$fogApiToken = 'mf...A=' $fogUserToken = '5Mz...NDY=' $fogServer = "IP ADDRESS GOES HERE" $headers = @{}; $headers.Add('fog-api-token', $fogApiToken); $headers.Add('fog-user-token', $fogUserToken); $BaseUri = "http://$fogServer/fog" $HostURL = $baseUri +"/host/" $HostResult = Invoke-RestMethod -Uri $HostURL -Method GET -Headers $headers -ContentType "application/json" $ThisHost = $HostResult.hosts | ? name -eq $ENV:COMPUTERNAME $PrimaryUser = $ThisHost.Inventory.PrimaryUser.Trim()