Adding or deleting shortcuts from the WinX folder doesn't seem to work anymore as it did in the past. It no longer works for me on 24H2 with the latest updates.
Adding a shortcut to any of the Group Folders in %LOCALAPPDATA%\Microsoft\Windows\WinX results in the entry not appearing on the WinX Menu. I tried using a few of the programs out there that let you do this to no avail. Manually adding them doesn't work either. I don't use any 3rd party software...
Another thing I just realized is that when I set my BIOS to the Intel defaults it also turned on Fast Boot. Could Fast Boot have bypassed loading some stuff that was causing my BSOD?
Well, I finally got the repair install to work. I think my problem boiled down to two things.
1. It appears using the Phison controller drivers enabled me to boot.
2. I had to set my BIOS to the Intel defaults..This mode is Intel's response to the problems with the 13900k and 14900k CPU's...
Fast startup is already disabled. Already did a chkdsk /f /r with no errors found. BTW, I installed the Phison drivers again and I have no problems with them, go figure. Will give the remaining two suggestions a try shortly. Also keep in mind that a clean install works flawlessly but I don't...
Tried that already. Perhaps the update process is installing incompatible storage controller drivers. My Windows drive is on a nvme ssd. I use the standard NVM Express Controller drivers for these drives. If I try to update these storage controller drivers in Device Manager Phison drivers are...
As mentioned once I get the BSOD the damage is done already. After I fix the boot stuff and reboot again Windows rolls back the update. Same thing would probably happen if I restored the boot partition from my disk image. Also, correct me if I am wrong, but the boot process is more than just the...
I am on 2801. As I mentioned after I get the first BSOD after the in place update or repair update reboots I have to fire up a Windows USB PE where I can fix the BCD records. If I don't the next reboot will result in the same BSOD. This is telling me the update is screwing around with the boot...
Disabling Vt-d did not help. Every subsequent reboot ends up with the same BSOD. The only way to get a good boot is to boot up my Windows PE USB drive and rebuild the boot record. However, when my machine successfully boots up it reverts back to my previous version because of the BSOD. As I...
I also have another related option enabled called “Enable IOMMU during boot”. I will give your suggestion a try after I make a disk image of my boot drive just in case I run into the BSOD again.
BTW.. Does disabling these options affect Windows in other ways that might not be beneficial to me?
I have two options in my BIOS that might be the option you mentioned. Vt-d and 'Intel VMX Virtualization Technology. Both are enabled. Nothing in the BIOS with the name you mentioned. I am somewhat hesitant to believe that these options being enabled would cause my problems as they are also...
Tried Option 1 also. Thinking some more on this problem I recall that after I got the BSOD I restarted my machine and got the same BSOD again. I did not get the automatic revert back to my old version. I booted up a Windows PE on a USB drive and rebuilt the boot records. After doing so and...
I've been trying to do an in place upgrade of my Windows 11 system to see if it will fix some issues I am having. I have tried the 'old' in place upgrade using a 24H2 ISO and also tried the newer Settings/System/Recovery Fix problems using Windows Update /Reinstall feature.
The upgrade goes...
In all probability Defender is still on your system but made inactive by BitDefender unless they found a way of getting rid of it completely which I doubt.