click-click

Version 19 no longer installs correctly on a 26100.1 system. The taskbar is hung and keeps looping on a msg to hold down ESC to keep it from loading, but that doesn't stop the hang. Killed explorer and ran the v16 install and taskbar is back to normal. It seems v19 is not downward compatible anymore.

Please read my OP entirely. Been there, done that. So what's the fix?

I don't think any of these apps will install drivers for a VM when converting (I've already tried some others). Since I already have a bootable working VHD there is no need for me convert unless there are apps that actually redo the storage drivers to work in a VM which I doubt. Finding the non-compatible driver(s) in the VHD is the problem.

I have an updated W7 vhd that I boot loacally and I want to now use it in a VM (VBox). Since the BCD for booting was loacated outside of the vhd, I used Winntsetup to redo the BCD as shown below. The problem is, when I use the vhd in a VM, it starts to boot, but BSODs with 7b. When I try safe mode, it also abends. The last entry I see on the console before the BSOD is Classpnp.sys which is a storage class driver. So I assume I have a disk or controller driver installed in the vhd that doesn't work in a VM which may be causing the crash. @JFX or anyone else that might know how to resolve this, or something to try, please let me know.

If I remove a program from the start list, How do I get it to display again in the list? One my system, if I remove a program from the list, using it again later doesn't make it show up again in Start

I am using toolbars with StartAllBack. My quicklaunch toolbar is for my selected Apps. I have another toolbar that is created by Lenovo Power Manager which adds a useful Battery object. If I checkmark that toolbar to show in the taskbar, the SAB start icon tends to disappear under certain circumstances. It reappears in different situations such as mousing over the start icon or clicking on an empty space on the taskbar. If I uncheck the Power Manager Toolbar, none of this happens and the start icon never disappears. Is it possible for SAB to make thw start icon stick and not disappear? Happens too if the taskbar is unlocked.

No idea. I encountered the problem clean installing 26100.1 It's been turned off here ever since.

It's called Smart App Control and can be turned off in Defender or registry (0=Off 1=On 2=evaluation). Another half-baked attempt by Ms to tighten security that only gets in the way. https://support.microsoft.com/en-us/windows/smart-app-control-frequently-asked-questions-285ea03d-fa88-4d56-882e-6698afdb7003

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