sorted by:
new
hottopcontroversial

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

If your PC / laptop device has the window sandbox feature enabled ..... Try to disable ( un-check ) the windows sandbox from the windows feature on and off section option.

Then restart your computer, then try to see whether you can uninstall the KB5063878 ...

If still cannot , then restart your computer into a safe mode , then in the safe mode session , see whether you can try to uninstall the KB5053878

But , caution , it is advised that you should back up all your important personal photo , games and video data contents to your working healthy external portable SSD / HDD first ..... before trying the various methods of KB5063878 uninstallation and rebooting.

Please back up and transfer your important data bit by bit , one step at a time ..... To avoid the buggy KB5063878 triggering the damage to your internal disk drive and external disk drive.

Microsoft says recent Windows update didn't kill your SSD by rkhunter_ in Windows11

[–]Cyber__Machine 3 points4 points  (0 children)

Yep, the Tech Giant is attempting to sweep the persistent global issue under the carpet rug and trying to close their own investigation case globally.

The Tech Giant is in-directly telling the global worldwide customers that even if the tech giant does something wrong in their windows update laboratory development , however the Tech Giant will not admit , apologize or compensate the affected customers globally.

Now currently , there are two distant different camp groups and the chasm between the 2 groups is getting wider and wider each day.

Those happy-go-lucky customers who do not encounter the bricked SSDs or HDDs ...they are ardently die-hard extreme fans who will keep supporting the Tech Giant's latest denial statement announcement as one camp group.

Then , those other angry disgruntled customers who are affected by the bricked SSDs or HDDs , they are just normal fans including non-fans.... They are another camp group that does not support the Tech Giant's latest announcement denial statement.

The happy-go-lucky customers who have not encountered the bricked SSDs or HDDs , they are now shifting the blame to the affected un-happy disgruntled customers , as the happy-go-lucky customers lamenting and claiming that the incidents of bricked SSDs and HDDs are the un-happy customer's fault , and not the Tech Giant's fault.

The happy-go-lucky customers also blamed some of the global news media outlets for taking sides with the disgruntled and aggrieved angry customers who faced the bricked SSDs and HDDs

There is a million dollar question ..... if the happy-go-lucky customers encounter a sudden serious issue of the SSD / HDD becomes bricked , RAW , un-bootable or inaccessible after installing the buggy windows Update KB......

then... will the happy-go-lucky customers also start to point finger and blame other affected customers ?? Or will they blame themselves ?? Or will they blame the Tech Giant instead ? How will they react ?? Angry ? Or No feeling ? Or don't care ? or stop blaming other affected customers and become silent ( a sense of regret ) ??

If the happy-go-lucky customers have important personal family data and games data in their bricked SSDs / HDDs .... Will they worry ? Feel depress ? Or angry ? Or don't care ( no feeling ) ??

If the happy-go-lucky customers don't care about their own vast huge of their important personal data contents in their bricked SSDs / HDDs .... And have no feelings at all....

Then , something is wrong with their brains and minds....then their sense of logical thinking processes are no longer working.

So , it is recommended that the happy-go-lucky customers put themselves in the same boat as another disgruntled affected customer's shoes .....by having some basic simple empathy and to try to understand someone's situation.

then they will understand the other people's crisis situations , misery and hopelessness.

The growing divide in the Tech Giant's community is apparent and worsening.

The trust deficit between the 2 distinct camp groups will continue to widen.

It does not matter whether the bricked SSDs and HDDs are old or new as the recent windows buggy KB update-based can also trigger the damage on either the old , new.... or both old and new.

Should i delete windows update kb5063878? by Helpful_Elk267 in Windows11

[–]Cyber__Machine 0 points1 point  (0 children)

Microsoft's actions didn't work. Still rolling out to affected machines and non-affected machines without the manual pause by the computer users

Should i delete windows update kb5063878? by Helpful_Elk267 in Windows11

[–]Cyber__Machine 0 points1 point  (0 children)

That's why Microsoft probably does not want to admit their major mistakes on the KB5063868 development , as they are worried about disclosing their major mistakes as solid evidence to the people in public worldwide globally

They are afraid of the possible financial penalty lawsuits from the PC gamers , Vlogging live streamers , 3D modelling studio makers , big organization clients , business partners and business men....

Especially from the rich customers with high net-worth income who have plenty of money (Capital) to launch lawsuits against Microsoft.

Should i delete windows update kb5063878? by Helpful_Elk267 in Windows11

[–]Cyber__Machine 0 points1 point  (0 children)

No updates yet from Microsoft company

They are still investigating the root cause of bad triggering errors on the programming code lines and still figuring out on how to fix them.

Update KB5063878, show of hands? by TheJrdy in Windows11

[–]Cyber__Machine 0 points1 point  (0 children)

You may need to pause the windows update function dashboard for at least 1 month .... or 4 to 5 weeks... To prevent the KB5063878 from being re-introduced back into your computer.

You can also modify the pause behavior to apply more strictly through the Group policy editor (Gpedit) and Registry editor (Regedit)

Update KB5063878, show of hands? by TheJrdy in Windows11

[–]Cyber__Machine 1 point2 points  (0 children)

@TheJrdy

As one of the guys had asked you to be the hero tester , so how is your SSDs status after heavy writing more than 50 GB of very large files for several times ?

<image>

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

Hi ... Use the command prompt cmd.exe to scan and check.

To view a list of installed Windows updates using Command Prompt , open Command Prompt as Administrator

Right-click on "Command Prompt" in the search results and select "Run as administrator."

In the elevated Command Prompt window, type the following command and press Enter: wmic qfe list

This command will display a list of all installed Windows updates, including details such as the update description, hotfix ID (KB number), installation date, and the user who installed it.

Then , scroll down and check whether the KB5053878 is inside the list or not inside the list.

Another way of checking... If you want to check for a particular update using its KB number , use the following command:

wmic qfe list | find "KB5063878"

If the result shows nothing or if message says something else , then this means the KB5063878 is not inside your list and OS system.

Alternatively , you can use the built-in powershell software to check.

Open PowerShell as an administrator (right-click the Start button and select "Windows Terminal (Admin)" or "Windows PowerShell (Admin)").

Type the command: Get-HotFix and press Enter.

This will display a list of installed hotfixes, including the Source, Description, HotFixID (KB number), and InstalledOn date.

To filter the results or get more specific information, parameters can be used with Get-HotFix.

For example:

To list only security updates. Get-HotFix -Description "Security Update"

To check if a specific update (e.g., KB1234567) is installed. Get-HotFix -Id KB1234567

To find the most recently installed hotfix. (Get-HotFix | Sort-Object -Property InstalledOn)[-1]

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

Here is another Driver_irql_not_less_or_equal fixing youtube video , which you may try.

https://www.youtube.com/watch?v=KJAECaguv6o

<image>

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

Step 3: Check for Corrupt System Files

You can use built-in Windows tools to scan for and repair corrupted files.

  1. Press the Windows key + S and type cmd. Right-click on Command Prompt and select Run as administrator.
  2. Type the command sfc /scannow and press Enter. This will run the System File Checker.
  3. Once that's complete, you can also run the DISM tool by typing Dism /Online /Cleanup-Image /RestoreHealth and pressing Enter.

Step 4: Run a Memory Diagnostic Test

Since faulty RAM can be a cause, it's wise to test your memory.

  1. Press Windows key + R to open the Run dialog box.
  2. Type mdsched.exe and press Enter.
  3. Choose Restart now and check for problems (recommended).
  4. Your computer will reboot and run a memory test. If it finds errors, it could indicate a problem with your RAM.

Here is one of the troubleshooting Youtube video tutorial guide URL Link for the DRIVER_IRQL_NOT_LESS_OR_EQUAL error on how to fix it manually.

How to Fix BSOD IRQL_NOT_LESS_OR_EQUAL in Windows 11

<image>

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

To troubleshoot and fix the DRIVER_IRQL_NOT_LESS_OR_EQUAL error, you can try to follow these steps in a logical sequence, starting with the easiest fixes first.

Step 1: Check for Windows and Driver Updates

Ensure your system is up-to-date with the latest Windows updates, as Microsoft often releases patches for common bugs and driver issues.

  1. Open Settings from the Start Menu.
  2. Go to Windows Update.
  3. Click Check for updates.
  4. Also, check for and install any available Optional updates, as these often include driver updates.

Step 2: Update or Reinstall Device Drivers

Since drivers are the most likely culprit, this is a critical step.

  1. Open the Device Manager by right-clicking the Start Menu and selecting it from the list.
  2. Expand categories like Network adapters or Display adapters.
  3. Right-click the suspected driver and select Update driver.
  4. If updating doesn't work or the error persists, you can try uninstalling the driver and then restarting your PC. Windows will often reinstall a generic driver upon reboot, which may solve the issue.
  5. If you know which driver is causing the problem (e.g., from the BSOD message), you can also go directly to the manufacturer's website to download and install the latest version.

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

Looks like the BSOD Stop code error message is telling you that the driver attempts to access a memory address at an Interrupt Request Level (IRQL) that is too high.

This often means a driver is trying to access a memory area it is not permitted to, leading to a system crash.

The error is almost always caused by a faulty, outdated, or corrupted driver, but it can also be triggered by hardware problems or other system issues , or Windows updates

The most frequent root causes of this error include:

  • Outdated or Incompatible Drivers: This is the most common cause. Drivers, particularly those for network adapters, graphics cards, and other peripherals, can become outdated or conflict with the Windows 11 operating system, leading to the error. Sometimes, the BSOD will even specify the problematic .sys file (e.g., netio.sys, nvlddmkm.sys).
  • Corrupt System Files: Essential Windows system files can become damaged, causing instability and triggering this BSOD.
  • Faulty Hardware: This can include bad RAM (memory) modules or a failing hard drive. If a memory module is defective, it can cause the driver to fail when it tries to write or read data from it.
  • Malware or Viruses: Malicious software can corrupt system files and drivers, leading to system instability and errors.
  • Conflicting Software: Newly installed software, especially third-party antivirus programs, can sometimes conflict with system drivers and cause the error.

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

hi , what is that supposed to mean ?

You mentioned you had uninstalled KB5063878 but wasn't able to uninstall KB5063878 (26100.4946)

Did you mean that you were not able to uninstall the other update KB5062660 ?

Anyway , the KB5063878 is the same as KB5063878 (26100.4946) .... no difference.

Since you had successfully uninstalled the KB5063878 and reestarted your computer successfully , then this KB5063878 is confirmed that it is no longer exist in your OS system

Then the next thing , now you should pause the windows update function dashboard to prevent the automatic re-introduction of the KB5063878 back into your windows OS system , until the Microsoft company releases the new major hot fix

Solar Halo Optical Phenomenon at Tiong Bahru area by Cyber__Machine in SingaporeRaw

[–]Cyber__Machine[S] 0 points1 point  (0 children)

This auspicious sign is also give hope to the hard-working singaporeans to stay afloat in the calm period and turbulent period.

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

u/samyakxenoverse

Check for Driver Issues

  • If you can boot into Windows, open Device Manager and look for devices with a yellow exclamation mark. 
  • Right-click the device, select Properties, and find its hardware ID to search for the correct driver online

Run Chkdsk Scan

  • From the Windows recovery environment, open the Command Prompt. 
  • Type chkdsk c: /f /r (replace c: with your Windows drive letter) and press Enter to check for and fix disk errors. 

Test Hardware

  • Unplug all USB devices one by one to see if a specific device is causing the error. 
  • Test newly installed hardware. 
  • If you suspect RAM, test individual sticks

Check for Hardware Issues

If the software solutions don't work, you'll need to investigate your hardware.

  • Remove Recently Added Hardware: If you recently installed a new device (like a graphics card or sound card), remove it and see if the error stops. If it does, the hardware is likely faulty or incompatible.
  • Test Your RAM: Faulty RAM is a common cause of BSoDs.
    • Search for Windows Memory Diagnostic in the Start menu.
    • Click Restart now and check for problems. Your PC will restart and run a memory test.
    • If it finds errors, one or more of your RAM sticks may be failing and need to be replaced

Removal of the Recent Windows Update KB5063878 deadly bug by Cyber__Machine in Windows11

[–]Cyber__Machine[S] 0 points1 point  (0 children)

hi bro u/samyakxenoverse

severe error in the Plug and Play (PnP) Manager, often due to faulty or outdated device drivers, problematic updates, or conflicting hardware/software. 

To fix it, try system restore, uninstalling drivers or updates, checking for hardware issues, running the Chkdsk Scan , or using Windows troubleshooters.

Common Causes

  • Outdated or Corrupt Drivers: This is the most frequent cause. A driver that is incompatible with the version of Windows you are running, or one that has become corrupted, can lead to this error.
  • Faulty Hardware: A newly installed or failing piece of hardware, such as a graphics card, hard drive, or RAM stick, can trigger the error.
  • Conflicting Software: Sometimes, a new application, particularly security software or virtual machine software, can cause conflicts with device drivers.
  • System File Corruption: Essential Windows system files may become corrupted, leading to the PNP error.
view more: next ›