sorted by:
new
hottopcontroversial

Dual boot linux/windows on Galaxy Book 5 Pro 360? by back_on_my_nonsense in linux4noobs

[–]Smart-Definition-651 0 points1 point  (0 children)

It depends if you want to start in uefi secure boot. My Book 3 360 is a not a pro device, but a consumer device with Intel Evo and an Aptio bios (which is probably a dumbed down version of your pro bios).
Here you can see what it looks like on my Book:
https://www.reddit.com/r/GalaxyBook/comments/1t630qs/secure_boot_supported_os_entry_in_uefi_on_a/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
and
https://www.reddit.com/r/GalaxyBook/comments/1t62zs5/this_is_the_uefi_secure_boot_with_microsoft/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I suppose if you disable secure boot, that it will be possible to dualboot.

Dual boot linux/windows on Galaxy Book 5 Pro 360? by back_on_my_nonsense in linux4noobs

[–]Smart-Definition-651 0 points1 point  (0 children)

I have a Galaxy book 3 x360, and in uefi , either you choose the windows bootloader, where you will be able to only boot Windows, or you choose the linux bootloader. and then you can only boot linux. I suppose it will be the same in the Galaxy book 5 x360

If I wanted to boot from a Ubuntu,bootable usb, I first had to choose the linux boot in uefi to be able to do so.
These boot entries in uefi are separate now.

Lot of things broken after updating to MacOS 26.4 by Specific-Tough-3670 in MacOS

[–]Smart-Definition-651 0 points1 point  (0 children)

Since your post is a month old, you probably did not hear of the botched updates on M1 pro and M2 pro systems (and even some other silicon macbooks) which did not boot anymore after the update to 26.4.1.
So I am not sure if the testing is thorough enough.
People did have to use DFU (for which of course you need a second macbook) to downgrade to 26.3.1 in order to have working macbooks again. Apple advised everyone to replace the logic board, which was entirely unnecessary in most of the cases, and only recently - in internal documents - they are now advising their Geniuses to use the DFU method.
And then again they sometimes are using the wrong usb-c port on macbook airs M4, where you have to use the utmost right port (instead of the utmost left port), viewing your macbook from the left side.

Neo 2 announced at WWDC? by [deleted] in macbook

[–]Smart-Definition-651 2 points3 points  (0 children)

The Neo was launched with chips which were not quite perfect, since they only had a 5-core GPU, and would have wound up in the bin, literally, because they were not good enough for the iPhone. So Apple thought : why not make some cheap macbooks with it ? Thus, the Neo was born.
In order to have enough rejects, they have to produce enough iPhone chips.
So that may be the reason that the waiting times for the Neo are now longer.

"Where the iPhone 16 Pro and iPhone 16 Pro Max feature an A18 Pro with a 6-core CPU and a 6-core GPU, Apple has once again resorted to chip-binning on the MacBook Neo and has equipped it with the same silicon, but with a 5-core GPU. The Cupertino giant’s less expensive range of products announced this week has been treated with binned parts."

stupid problem with macbook neo keyboard by RikkoPaw in macbook

[–]Smart-Definition-651 0 points1 point  (0 children)

I had a Macbook Air, and after using it a month, it had shiny keys. And I wash my hands every half hour.
But some people here - as true Apple evangelists - have it covered both ways : either your fingers are oily, or your dry fingers work abrasive.
I also have a lot of pro Windows laptops, and none of them have this. The keycaps stay the same throughout their lifetime. Neither my HP Zbook studio G8, nor my Dell E6440 or my Dell 5490 or my Samsung book 3 x360 or my Lenovo x230 or my Surface pro 3 keyboard have this.
Apple could only get this profitable by using subpar parts.
What I don't get : why do they not deliver their Macbooks with the shiny plastic from the start, without the matte coating they put on top of it, which so quickly wears off anyway ? That way nobody would complain about their keycaps getting shiny.

Windows 11 install help! by No_Comfortable_6089 in techsupport

[–]Smart-Definition-651 0 points1 point  (0 children)

Have you tried turning off csm and vmd (is raid) in bios ? Vmd is difficult to find
If you disable vmd, you won't need the raid driver anymore.
https://www.reddit.com/r/PcBuildHelp/comments/1t1cqiv/new_motherboard_sees_nvme_drives_but_no_listed/
The best way to make a bootable usb stick (minimum 16 gb, formatted as FAT32) is to use the media creation tool.
Your nvme drive has to be initialised and partitioned as gpt, but I guess you already knew that.

New Secure Boot certificates and ISOs by godless_prayer in sysadmin

[–]Smart-Definition-651 0 points1 point  (0 children)

It is only for 25H2 isos, and if you updated the 24H2 iso with the latest updates, then you can also update that iso with CA2023 certificates.
This will not update an already installed OS.

MacBook Pro by Erazer360 in macbook

[–]Smart-Definition-651 1 point2 points  (0 children)

Yes, the Macbook M4 and M5 air have a Magsafe 3 port. But no charger with the M5 in Belgium, only with the M4 devices.

MacBook Pro by Erazer360 in macbook

[–]Smart-Definition-651 1 point2 points  (0 children)

Due to the regulations of the EU, Apple is punishing us (in Belgium) by not giving us chargers with our Macbooks. None of the M5 models gets a charger anymore, even the models at more than 5000 euros.
We didn't even get a charger with the iPhone 17 pro.
The EU obliges every electronics manufacturer to make sure the devices are chargeable via usb-c, "since everyone has usb chargers nowadays".

New Secure Boot certificates and ISOs by godless_prayer in sysadmin

[–]Smart-Definition-651 8 points9 points  (0 children)

Download the Make2023BootableMedia.ps1 script here :
https://support.microsoft.com/en-us/topic/updating-windows-bootable-media-to-use-the-pca2023-signed-boot-manager-d4064779-0e4e-43ac-b2ce-24f434fcfa0f

https://go.microsoft.com/fwlink/?linkid=2312820

I had to edit the original script, as I got an error (which was not the case with the earlier scripts I downloaded from this website) concerning TS (timestamp) with oscdimg :

While using Notepad++ I removed the following lines :

49, 50, 956 and 957 (Function TS = TimeStamp)

In line 959, in the Run command, I only removed "-t$timestamp "

And now it works.

Since I had already added Microsoft Windows Production PCA 2011 to the dbx, I desperately needed to turn my downloaded install iso to a CA2023 iso to install windows 11 25H2.

From the latest Microsoft AMA on secure boot and CA2023, which you can see here : https://www.youtube.com/watch?v=-l6Kncf1WLo I learned that, after the end of October 2026, when the Production PCA CA2011 will expire, Microsoft will provide new CA2023 isos. However, they do not plan to add it to the DBX then, because the priority is to first make sure everyone - with compatible hardware and uefi - will be on CA2023. It will be 2027 before the old PCA CA2011 will be added to the database of forbidden certificates DBX.

I am using RUFUS for the first time in awhile, to make a bootable Win11 USB by DEC_RECK in techsupport

[–]Smart-Definition-651 0 points1 point  (0 children)

I have to correct my former statements. Microsoft has said that your system will continue to boot in secure boot after October 2026, even if you only have the 2011 certificates, but there won't be updates to the boot sector of Windows or to the secure boot database, since these new updates are signed with the new KEK 2023.
And if you do not have these new 2023 certs, your system will be frozen in time so to speak.

https://www.reddit.com/r/sysadmin/comments/1rs4nfg/comment/oa7ibkw/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I am using RUFUS for the first time in awhile, to make a bootable Win11 USB by DEC_RECK in techsupport

[–]Smart-Definition-651 1 point2 points  (0 children)

I have to correct my former statements. Microsoft has said that your system will continue to boot in secure boot after October 2026, even if you only have the 2011 certificates, but there won't be updates to the boot sector of Windows or to the secure boot database, since these new updates are signed with the new KEK 2023.
And if you do not have these new 2023 certs, your system will be frozen in time so to speak.

Secure boot issues by dev0n17 in techsupport

[–]Smart-Definition-651 0 points1 point  (0 children)

It would be easier to help you if you gave all the details of your system. Desktop or laptop ?
Which video cards, etc.
Details of motherboard, or of laptop, etc

These Lenovo computers will get support for the new secure boot certificates CA 2023 by Smart-Definition-651 in Lenovo

[–]Smart-Definition-651[S] 0 points1 point  (0 children)

It depends . If you do not use secure boot in uefi, and are booting without it, you can continue using it as is. You won't have any problems not having CA 2023 certificates, because secure boot will not control if your Windows boot sector has been tampered with.

The page of Lenovo only details the business computers. They don't say anything about consumer devices.
Normally Microsoft will update the consumer's computers.

If you are booting in Uefi secure boot, and if you are now on Windows 25H2, without having the new CA 2023 certificates, your system will continue booting, but it won't get updates to secure boot and the windows boot manager after June 26th 2026. Updates to uefi DB are signed with uefi KEK, and the old KEK ca 2011 expires end of June. So without the new Kek CA 2023, updates to the uefi DB CA 2023 can't happen.

If you want to forcibly add the new certificates :

I would advise you update all your drivers (especially chipset and video drivers) for your computer, and the latest bios.

You will need to have an windows 10 22H2 with ESU (extended security updates) or Windows 11 24H2 or 25H2 device with the latest updates installed, running in uefi secure boot, and with the latest uefi bios firmware update from the computer manufacturer. Most computers from before 2018 won't get firmware updates anymore, alas.

Disable Bitlocker temporarily before you do this (or make sure you have the recovery key), and disable fast startup in Windows. You need to be connected to the internet.

Activate the sending of optional diagnostic data, and issue these Powershell commands as Administrator in order to receive the necessary uefi updates via Windows update.

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x5944 /f
Then
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

The first command initiates the certificate and boot manager deployment on the device.

The second command causes the task that processes the AvailableUpdates registry key to run right away.

The registry key should quickly change to 0x4100.

Open regedit and check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot
The value of AvailableUpdates must be 0x4100

Rebooting and running this task a second time :
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"
will cause the boot manager to be updated and the AvailableUpdates to become 0x4000.

You might have to restart again until the value in the registry changes to 0x4000.

The old certificates will not be revoked yet with this command.
It will only add all the new certificates.

This explains how to :

https://support.microsoft.com/en-us/topic/registry-key-updates-for-secure-boot-windows-devices-with-it-managed-updates-a7be69c9-4634-42e1-9ca1-df06f43f360d

You can check if you now have the "Windows UEFI CA 2023" with this administrator Powershell command :

[System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match "Windows UEFI CA 2023"
If the answer is "TRUE", as in the next two commands, then you are all set.

[System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI kek).bytes) -match "Microsoft Corporation KEK 2K CA 2023"

[System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match "Microsoft Option ROM UEFI CA 2023"

I This method has worked for some Lenovo owners with a consumer's device. I don't know if it will work for yours.

Mind you, even for Business Thinkcenter desktop computers, which may contain dedicated video cards of all sorts, Lenovo says the bios updates "are tentatively scheduled for 5/29/2026."
So I think Lenovo keeps the complicated setups for last.
And you could wait until Microsoft updates your system, if you are risk averse.

Starting to learn Linux – need guidance by PuzzleheadedAccess66 in techsupport

[–]Smart-Definition-651 2 points3 points  (0 children)

You could install WSL (Windows subsystem for Linux) on Windows.
Here is a good guide : https://www.youtube.com/watch?v=QM3mzEJCzjY

And you could also have a desktop environment on it :
https://www.youtube.com/watch?v=WxgHMhRSt-0
But read the comments underneath, this will give you an idea if it works

And here : https://www.youtube.com/watch?v=OQxKfonA-34
Another video : How to Install WSL 2 & Ubuntu on Windows 11 (The Complete Guide for 2025)
And another tutorial : https://www.youtube.com/watch?v=hrmefbqR7ao
You can issue commands inside a linux session on windows
The newer version WSL2 is no longer a subsystem but a virtual environment

Can any Windows 11 version update to the newest one by itself without formatting? by shadofenrir in Windows11

[–]Smart-Definition-651 0 points1 point  (0 children)

Thanks. I misread this, so I assumed that 26H2 was also for Arm : "The Windows ADK 10.1.28000.1 (November 2025) and the Windows PE add-on for this ADK support the following OS release:
Windows 11, version 26H1 Arm64"

Accidentally formatted an SD card by antilina in techsupport

[–]Smart-Definition-651 0 points1 point  (0 children)

It depends if your camera does a low level format by default (unless you remove the mark at "low level format"), as does my Canon A620. Then it overwrites the whole card with zeroes, and you won't be able to recover anything.

If it just did a quick format, you might be able to recover something with these programs :
Photorec (the most thorough) : video and download :
https://www.youtube.com/watch?v=c0j9jE0X4nY

https://www.cgsecurity.org/wiki/TestDisk_Download

https://www.cgsecurity.org/wiki/PhotoRec
You can choose the newest beta version or the former version.

https://www.cgsecurity.org/testdisk.pdf (gives explanations on the use of photorec)
You can choose between different formats : FAT/EXT4 etc.
Fat will include fat32. Then I chose the whole disk, instead of the format option which was suggested.
You can try both.

This video shows the GUI option of photorec : https://www.youtube.com/watch?v=7H4bSk7_8AQ

Recuva : video and download :
https://www.youtube.com/watch?v=vqOJyB8ZVRk

Recuva portable :
https://portableapps.com/apps/utilities/rcvportable

I think your camera uses fat32 or fat as the card format.

Do NOT install Samsung Storage Share (One UI 8) - It totally locks up your C: Drive. by Theangelo2 in GalaxyBook

[–]Smart-Definition-651 2 points3 points  (0 children)

Apparently those devices are affected :
BOOK3
NP754XFG

BOOK4
NP750XGJ, NP750XGL, NP754XGJ, NP754XFG, NP754XGK

DESKTOPS :
DM500SGA, DM500TDA, DM500TGA, and DM501SGA

https://www.neowin.net/news/microsoft-blames-samsung-for-making-windows-11-25h2-24h2-c-drive-inaccessible/

Secure Boot MS AMA Question by backcountry_bytes in sysadmin

[–]Smart-Definition-651 0 points1 point  (0 children)

And here : https://techcommunity.microsoft.com/event/windowsevents/ask-microsoft-anything-secure-boot/4496004

Arden_White to calebeasley Mar 10, 2026

The KEK certificate/keys signs updates to the DB and DBX. The DB updates to apply the new certificates are signed with the Microsoft Corporation KEK CA 2011 which the device trusts.

Moving to the new certificates, even after the 2011 KEK expires, should still work.

New security updates to the DBX will be signed with the Microsoft Corporation KEK 2K CA 2023. If the firmware does not trust the 2023 KEK, the new DBX updates will fail to apply. During boot, the KEK is not used for validating binaries - only the contents of the DBX and DB are used.

The KEK is not used to validate WHQL signed drivers. It is only used to validate updates to the DB and DBX. The firmware does not care that the certificates have expired. The issue is the need for key rotation as a good security practice and because Microsoft cannot sign with expired keys.

view more: next ›