Dang. Didn't know that `bootcfg` would add another boot entry instead of overwriting the current one.
Also: I added the top one as `C:\Windows`, so why does the boot manager not show that anywhere?
`msconfig` shows it properly.
Somehow this Dell system would not boot with the stock configuration of `\WINDOWS`, but `C:\Windows` worked fine. Not sure why.
Without the `C:` bit, it would not boot and Automatic Repair not only failed to repair, it also did not persist the `StrTrail.txt` file (when going to the command prompt it was not to be found on any of the drive letters).
Running `bcdboot C:\Windows` on the recovery partition fixes the boot problem by specifying the drive letter to boot from.
I did not know this would add a second BCD entry using the same caption, so that was confusing me as I assumed (the mother of all mistakes) it overwrites.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Resultaat is tot en met 9 december, maar je Tweet van vanmorgen ontbreekt.
Ik moest de archief-link sturen, want de zoek-link met URL erin posten mag niet meer.
Deze link mag wel.
Oh, zie net dat dan toen een plaatje was omdat je de link niet meer kon sturen. Dan klopt het zoekresultaat inderdaad, maar ook: de zoeklink kun je dus ook niet meer sturen.
When creating an account using Edge on Windows 10 (latest version of both; no plugins; Microsoft Defender in default settings), solving the puzzle loops back to
"Please solve the puzzle so we know you're not a robot."
I guess quite a few places still link to it and other blog posts, so it would be cool to know if it exists somewhere and if so notify people to update their links.
Does anyone know why this iqvw64e.sys file from @Dell is considered unsafe? It is signed by @IntelSoftware and resides in C:\Program Files\Dell\SupportAssistAgent\PCDr\SupportAssist\6.0.7033.2285\iqvw64e.sys
iqvw64e.inf in the same directory: 04/06/2018,1.3.2.17
The English screenshot is from answers.microsoft.com/en-us/windows/… indicating "iqvw64e is a software component of Intel Network Adapter Diagnostic Driver" and @Windows suggesting to lower security settings (which makes the system less secure).
There is very little I can find on the "NALDevice" mentioned in the .inf file. "NAL device" gives me github.com/Exploitables/C… which should be fixed in the 1.3.2 version of the driver I have.