click-click

I noticed SAB has a lot of duplicate icons in the tray icons config section. Sometimes three sometimes 2. They may or may not be checkmarked. The icons are visible only once on the taskbar. I'm using a quicklaunch folder on the taskbar if that matters. Running with SAB 3.9.5

@JFX or whoever knows I have and EFI partition that does not show a drive letter. For -syspart:{X} can I use -syspart:HDD-0:1 to get WinntSetup to update the EFI BCD there? i.e. d:\ThinApps\WinNTSetup\WinNTSetup_x64.exe NT6 -sysPart:HDD-0:1 -tempDrive:Z: -sysLetter:-C: -bcd:EFI -silent -setup Also, I can't remember why I used -sysLetter:-C: Should it not be -sysLetter:C:

I had Classic context menus enabled and this also worked for all desktop objects such as This PC . I recently inadvertantly unchecked this item in Make it top notch. I re-enabled it, but now all desktop items still show the new context menu instead of the classic one. All other items not on the desktop show the classic menu after it was re-enabed. How do I also get back classic context menu for the items on the desktop? I'm at 3.8.13 and using Windows 11 Pro 22631.4460 or Windows 11 LTSC 26100.2314 Edit: I'm not sure if StartAllBack ever supported the issue describe above, but I may have applied the following reg file previuosly, which got undone by unchecking the Startallback Context menu option. reg.exe add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve The above command brings back the Classic contect menu for the Desktop items too.

Will a single license allow it to be used with different Windows systems on a multi-boot PC? My understanding is that the license is tied to the hardware, so if I use a multi-boot setup, the license will cover more than one StartAllBack install on that PC. Is that correct?

Did you not read my post above? CSM support for both with priority Legacy 1st and UEFI last. I tried a few things such as renaming the EFI directory as EFI_ and that is the only way up to now to make it use the BIOS boot BCD. As soon as I rename it back to EFI, it reverts to UEFI for the boot. The only other difference between the 2 flash drives is 128GB vs 256GB. The other thing I did was to restore the 100MB partition from the working 128GB flash to the other flash and that crashes. If I let WinNTSetup update the BCDs, the crash issue is resolved, but it still defaults to booting EFI

@JFX or anyone with and idea. I have 2 usb SSD flash drives that are set up to boot either BIOS or UEFI. Both have 2 partitons and the layout is 100MB FAT and the other NTFS for VHDs and wim files. I have a laptop that has CSM support and allows both BIOS and UEFI booting. The priority is Legacy first and UEFI 2nd. One flash works as it should and uses the BIOS boot BCD when booting. The other drive for some reason always ends up using the EFI BCD. I must have done something to that flash that causes this, but I don't know what. Both BIOS and EFI BCDs are pretty much identical on both flash drives. Any idea what's causing the boot process to use EFI instead of BIOS for that flash?

I don't know. Never tried it. I doubt it can be used for vhds

If the EFI BCD is configured correctly in the ESR partition, I don't see why the VHDs shouldn't boot. Unless you're doing this on different HW that require other drivers not installed in your VHDs. I don't know anything about svbus. If you mean the RamDisk option as an entry in the BCD, that is what I select to boot wim files.

VHDs only is not a problem. Same setup as what I did with the .wim files. Configure the bcd to point to the HD and partition with the VHDs. You can convert BIOS (MBR) drive to GPT (Windows Disk Manager), but the data on it needs to be deleted so make sure to backup the disk before doing the conversion. I only need UEFI for my new hardware. I won't be doing any conversions on my current disks.

From what I've been able to determine, all that is needed for UEFI is a 100MB FAT ESP partition to hold the the BIOS (if needed) and the UEFI system files used by the boot process. A recovery partition and an MSR partition aren't really needed. GPT also replaces MBR on that drive, but other drives can still be MBR. The windows BootMgr still works with a correctly configured BCD. I did a small test with the following layout: Hd1 (GPT), 100MB FAT ESP and 100GB NTFS with Strelec 10/11 wim files. Bootmgr lists both and both will boot. I will create a 3rd partition and use WinntSetup to install an OS there and see what happens. If what I've said is incorrect, please let me know what.

I am planning on getting a new laptop that that will only have the UEFI BIOS. It will be bare-bones without any OS with 2 SSDs. I understand a new partition layout will be required, but that's about all I know about UEFI. I've been living too long in the past. Previously, I would create and format an NTFS partition and apply my customized wim with WinNTSetup. What kind of partition layout do I need now before using WinNTSetup and will windows bootmanger still show a list of systems for multi-booting?

My win 8.1 vhd on the internal hdd has BootDriverFlags set to 0., but still boots fine from there. I checked the other hdd vhds and they look okay. I wiil need to check this when deploying a new VHD on an external drive to be sure it has the correct value. I always hold by breath when booting a new VHD

one last question for now Does WinNtSetup do anything with BootDriverFlags? The reason I ask is that restoring/copying a Hdd partition to a VHD to be used for booting from an external usb device will give you a BSOD with 'inaccessible boot device' or error code 0xc0000001 even though the VHD was added to the boot menu with WinNtSetup. This is caused by BootDriverFlags being 0 under HKEY_LOCAL_MACHINE\SYSTEM\HardwareConfig in the VHD. I had to set the flags to x'1c' so the the VHD would boot from the usb drive.

Ok, now I have a better understanding why booting may fail. I use Runscanner to edit a remote registry for simple reg entries such as REG_DWORD BootDriverFlags, but editing a REG_BINARY value via GUI is a pain, so I guess I'll let WinNTSetup do the work. Instead of using the GUI, I see a lot of options in the help for using CLI switches, so to get it right, what would be the command line needed for only updating without the GUI? I tried WinNTSetup_x64.exe -sysPart:Q: -tempDrive:Z: -sysLetter:-C: -bcd:ALL, but that still launches the GUI and ignores the switches. I want to update via script if possible. i.e Diskpart >create/mount VHD > DriveSnapshot restore to VHD > WinNTSetup > update VHD

Do you mean replacing the value from \DosDevices\C: in the mounted VHD with the value from \DosDevices\Z: in the active system where the mount was made?

How is the fix for this done? I was getting a BSOD c0000139 after restoring a HDD partition to a new vhdx. The BCD had the correct entries in the boot menu. I assumed an incorrect mountpoint caused the BSOD and wanted to know the procedure to correct it when not using WinNTSetup

Upgraded to 3.8.6 after windows update for August (26100.1457). The Start Menu icon may be missing on startup or disappears temporarily when clicking multiple times on an empty space on the taskbar. Right clicking can also cause this when no apps open. I'm using enhanced classic taskbar. I tried the various start icons and the all tend to disappear. Hovering over the blank area tends to bring it back after it disappears.

WinntSetup internally fixes mount points when applying an image to a vhd . How would I do this from the CLI without using the GUI? i.e. Fixing Mountpoints Writing driveletter mountpoint of new system drive: \DosDevices\C: --> 0x09A5A6D10000100000000000

The problem may be related to BootDriverFlags in HKLM\SYSTEM\HardwareConfig set to 0. Set it to hex 1c before booting vhdx. You will need to mount the vhdx and use a remote regedit to check to and change the setting .

@JFX Where do you take the names from from in a specified wim file such as the leaked w11 LTSC version? WinNTsetup shows Windows 11 Enterprise LTSC Canary, but DISM /get-wiminfo doesn't show Canary.

Seems to be working again after several LCU updates. Also added /XS parameter to runscanner.

Do you happen to know the bcdedit commands needed to do this? I'm unsure how to add a PE wim file so it will boot. I have a partition for booting different vhds. Do I update the bcd from there to add the wim? Edit: OK, got it to work. I was missing the boot.sdi.