Turn off error reporting in

How to Disable Error Reporting in Windows

Disable error reporting to Microsoft in Windows 11, 10, 8, 7, etc.

In This Article

Jump to a Section

The error reporting feature in Windows is what produces those alerts after certain program or operating system errors, prompting you to send the information about the problem to Microsoft.

You might want to disable error reporting to avoid sending private information about your computer to Microsoft, because you’re not connected to the internet all the time, or just to stop being prompted by the annoying alerts.

Error reporting is enabled by default in all versions of Windows but is easy to turn off from either the Control Panel or from Services, depending on your version of Windows.

Before doing this, please keep in mind that not only is it beneficial for Microsoft, but it’s also ultimately a good thing for you, the Windows owner. These reports send vital information to Microsoft about a problem that the operating system or a program is having and helps them develop future patches and service packs, making Windows more stable.

The specific steps involved in disabling error reporting depends significantly on which operating system you’re using. See What Version of Windows Do I Have? if you’re not sure which set of instructions to follow.

Disable Error Reporting in Windows 11 & 10

Use the WIN+R keyboard shortcut to open the Run dialog box.

Enter services.msc.

Right-click or tap-and-hold Windows Error Reporting Service.

Select Properties.

Choose Disabled from the menu next to Startup type.

Can’t select it? If the Startup type menu is grayed out, log out and log back in as an administrator. Or, reopen Services with admin rights, which you can do by opening an elevated Command Prompt and then executing the services.msc command.

Select OK or Apply.

You can now close out of the Services window.

Another way to disable error reporting is through Registry Editor. Navigate to the registry key you see below, and then find the value called Disabled. If it doesn’t exist, make a new DWORD value with that exact name.

You can make a new DWORD value from the Edit > New menu in Registry Editor.

Double-click or double-tap the Disabled value to change it from a 0 to a 1, and then save it by selecting OK.

Disable Error Reporting in Windows 8 or Windows 7

Choose System and Security.

If you’re viewing the Large icons or Small icons view of Control Panel, select Action Center and skip to Step 4.

Choose Action Center.

Select Change Action Center settings from the left side of the Action Center window.

Select Problem reporting settings from the Related settings section at the bottom of the window.

Pick one of the four options:

  • Automatically check for solutions (the default option)
  • Automatically check for solutions and send additional report data, if needed
  • Each time a problem occurs, ask me before checking for solutions: Choosing this will keep error reporting enabled but will prevent Windows from automatically notifying Microsoft about the issue. If your concern about error reporting is only privacy related, this is the best option for you.
  • Never check for solutions: This will fully disable error reporting in Windows.

There’s also a Select programs to exclude from reporting option that you’re welcome to explore if you’d rather customize reporting instead of completely disable it. This is probably more work than you’re interested in, but the option is there if you need it.

If you can’t change these settings because they’re grayed out, choose the link at the bottom of the window that says Change report settings for all users.

Choose OK on the Problem Reporting Settings window, and then again on the Change Action Center settings window. You can now close the Action Center window.

Disable Error Reporting in Windows Vista

Choose Start and then Control Panel.

Select System and Maintenance.

If you’re viewing the Classic View of Control Panel, double-click Problem Reports and Solutions and skip to Step 4.

Choose Problem Reports and Solutions.

Select Change settings on the left side of the window.

Choose one of the two available options:

  • Check for solutions automatically (the default option)
  • Ask me to check if a problem occurs: Choosing this will keep error reporting enabled but will prevent Windows Vista from automatically notifying Microsoft about the issue.
Читайте также:  Error applying hard drive changes

If your only concern is sending information to Microsoft, you can stop here. If you’d like to fully disable error reporting, you can skip this step and continue on with the remaining instructions below.

Select Advanced settings.

Choose Off under the For my programs, problem reporting is: heading.

There are several advanced options here that you’re welcome to explore if you’d rather not completely disable error reporting in Windows Vista, but for the purposes of this tutorial, we’re going to completely disable the feature.

Select OK.

Select OK on the window with the Choose how to check for solutions to computer problems heading.

You might notice that the Check for solutions automatically and Ask me to check if a problem occurs options are now grayed out. This is because Windows Vista error reporting is completely disabled and these options are no longer applicable.

Select Close. You can also close any other related open Windows.

Disable Error Reporting in Windows XP

Go to Start and then Control Panel.

Select Performance and Maintenance.

If you’re viewing the Classic View of Control Panel, double-click System and skip to Step 4.

Select System under the or pick a Control Panel icon section.

Select the Advanced tab.

Select Error Reporting near the bottom of the window.

Choose Disable error reporting.

We recommend leaving the But notify me when critical errors occur checkbox checked. You probably still want Windows XP to notify you about the error, just not Microsoft.

Select OK on the Error Reporting window.

Select OK on the System Properties window

You can now close the Control Panel or Performance and Maintenance window.



(PHP 4, PHP 5, PHP 7, PHP 8)

error_reporting — Sets which PHP errors are reported


The error_reporting() function sets the error_reporting directive at runtime. PHP has many levels of errors, using this function sets that level for the duration (runtime) of your script. If the optional error_level is not set, error_reporting() will just return the current error reporting level.


The new error_reporting level. It takes on either a bitmask, or named constants. Using named constants is strongly encouraged to ensure compatibility for future versions. As error levels are added, the range of integers increases, so older integer-based error levels will not always behave as expected.

The available error level constants and the actual meanings of these error levels are described in the predefined constants.

Return Values

Returns the old error_reporting level or the current level if no error_level parameter is given.


Version Description
8.0.0 error_level is nullable now.


Example #1 error_reporting() examples

// Turn off all error reporting
error_reporting ( 0 );

// Report simple running errors
error_reporting ( E_ERROR | E_WARNING | E_PARSE );

// Reporting E_NOTICE can be good too (to report uninitialized
// variables or catch variable name misspellings . )
error_reporting ( E_ERROR | E_WARNING | E_PARSE | E_NOTICE );

// Report all errors except E_NOTICE
error_reporting ( E_ALL &

// Report all PHP errors
error_reporting ( E_ALL );

// Report all PHP errors
error_reporting (- 1 );

// Same as error_reporting(E_ALL);
ini_set ( ‘error_reporting’ , E_ALL );


Passing in the value -1 will show every possible error, even when new levels and constants are added in future PHP versions. The behavior is equivalent to passing E_ALL constant.

See Also

  • The display_errors directive
  • The html_errors directive
  • The xmlrpc_errors directive
  • ini_set() — Sets the value of a configuration option

User Contributed Notes 27 notes

If you just see a blank page instead of an error reporting and you have no server access so you can’t edit php configuration files like php.ini try this:

— create a new file in which you include the faulty script:

( E_ALL );
ini_set ( «display_errors» , 1 );
include( «file_with_errors.php» );

— execute this file instead of the faulty script file

now errors of your faulty script should be reported.
this works fine with me. hope it solves your problem as well!

Under PHP 8.0, error_reporting() does not return 0 when then the code uses a @ character.

= $array [ 20 ]; // error_reporting() returns 0 in php =8

The example of E_ALL ^ E_NOTICE is a ‘bit’ confusing for those of us not wholly conversant with bitwise operators.

If you wish to remove notices from the current level, whatever that unknown level might be, use &

$errorlevel = error_reporting ();
error_reporting ( $errorlevel &

//. code that generates notices
error_reporting ( $errorlevel );

^ is the xor (bit flipping) operator and would actually turn notices *on* if they were previously off (in the error level on its left). It works in the example because E_ALL is guaranteed to have the bit for E_NOTICE set, so when ^ flips that bit, it is in fact turned off. &

(and not) will always turn off the bits specified by the right-hand parameter, whether or not they were on or off.

The error_reporting() function won’t be effective if your display_errors directive in php.ini is set to «Off», regardless of level reporting you set. I had to set

to keep no error reporting as default, but be able to change error reporting level in my scripts.
I’m using PHP 4.3.9 and Apache 2.0.

In php7, what was generally a notice or a deprecated is now a warning : the same level of a mysql error … unacceptable for me.

I do have dozen of old projects and I surely d’ont want to define every variable which I eventually wrote 20y ago.

So two option: let php7 degrade my expensive SSDs writing Gb/hours or implement smthing like server level monitoring ( with auto_[pre-ap]pend_file in php.ini) and turn off E_WARNING

Custom overriding the level of php errors should be super handy and flexible …

This article refers to these two reporting levels:

// Report all PHP errors (see changelog)

// Report all PHP errors

What is the difference between those two levels?

Please update this article with a clear explanation of the difference and the possible use cases.

E_NOTICE integer value is 6135

If you want to see all errors in your local environment, you can set your project URL like «foo.com.local» locally and put that in bootstrap file.

if ( substr ( $_SERVER [ ‘SERVER_NAME’ ], — 6 ) == ‘.local’ ) <
ini_set ( ‘display_errors’ , 1 );
ini_set ( ‘error_reporting’ , E_ALL );
// or error_reporting(E_ALL);

If you are using the PHP development server, run from the command line via `php -S servername:port`, every single error/notice/warning will be reported in the command line itself, with file name, and line number, and stack trace.

So if you want to keep a log of all the errors even after page reloads (for help in debugging, maybe), running the PHP development server can be useful.

Some E_STRICT errors seem to be thrown during the page’s compilation process. This means they cannot be disabled by dynamically altering the error level at run time within that page.

The work-around for this was to rename the file and replace the original with a error_reporting() call and then a require() call.

Ex, rename index.php to index.inc.php, then re-create index.php as:

require( ‘index.inc.php’ );

That allows you to alter the error reporting prior to the file being compiled.

I discovered this recently when I was given code from another development firm that triggered several E_STRICT errors and I wanted to disable E_STRICT on a per-page basis.

see more information about php 5.3 deprecated errors

I had the problem that if there was an error, php would just give me a blank page. Any error at all forced a blank page instead of any output whatsoever, even though I made sure that I had error_reporting set to E_ALL, display_errors turned on, etc etc. But simply running the file in a different directory allowed it to show errors!

Turns out that the error_log file in the one directory was full (2.0 Gb). I erased the file and now errors are displayed normally. It might also help to turn error logging off.

To expand upon the note by chris at ocproducts dot com. If you prepend @ to error_reporting(), the function will always return 0.

( E_ALL );
var_dump (
error_reporting (), // value of E_ALL,
@ error_reporting () // value is 0

this is to show all errors for code that may be run on different versions

for php 5 it shows E_ALL^E_STRICT and for other versions just E_ALL

if anyone sees any problems with it please correct this post

Note that E_NOTICE will warn you about uninitialized variables, but assigning a key/value pair counts as initialization, and will not trigger any error :
( E_ALL );

$foo = $bar ; //notice : $bar uninitialized

$bar [ ‘foo’ ] = ‘hello’ ; // no notice, although $bar itself has never been initialized (with «$bar = array()» for example)

$bar = array( ‘foobar’ => ‘barfoo’ );
$foo = $bar [ ‘foobar’ ] // ok

$foo = $bar [ ‘nope’ ] // notice : no such index

This is very useful to remember when setting error_reporting levels in httpd.conf:

Use the table above or:

( «error_reporting» , E_YOUR_ERROR_LEVEL );
echo ini_get ( «error_reporting» );

To get the appropriate integer for your error-level. Then use:

php_admin_value error_reporting YOUR_INT

I want to share this rather straightforward tip as it is rather annoying for new php users trying to understand why things are not working when the error-level is set to (int) «E_ALL» = 0.

Maybe the PHP-developers should make ie error_reporting(«E_ALL»); output a E_NOTICE informative message about the mistake?

To enable error reporting for *ALL* error messages including every error level (including E_STRICT, E_NOTICE etc.), simply use:

error_reporting() has no effect if you have defined your own error handler with set_error_handler()

[Editor’s Note: This is not quite accurate.

E_ERROR, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR and E_COMPILE_WARNING error levels will be handled as per the error_reporting settings.

All other levels of errors will be passed to the custom error handler defined by set_error_handler().

Zeev Suraski suggests that a simple way to use the defined levels of error reporting with your custom error handlers is to add the following line to the top of your error handling function:

It might be a good idea to include E_COMPILE_ERROR in error_reporting.

If you have a customer error handler that does not output warnings, you may get a white screen of death if a «require» fails.


function myErrorHandler ( $errno , $errstr , $errfile , $errline ) <
// Do something other than output message.
return true ;

$old_error_handler = set_error_handler ( «myErrorHandler» );

require «this file does not exist» ;

To prevent this, simply include E_COMPILE_ERROR in the error_reporting.


I always code with E_ALL set.
After a couple of pages of
= (isset( $_POST [ ‘username’ ]) && !empty( $_POST [ ‘username’ ])).

I made this function to make things a little bit quicker. Unset values passed by reference won’t trigger a notice.

function test_ref (& $var , $test_function = » , $negate = false ) <
$stat = true ;
if(!isset( $var )) $stat = false ;
if (!empty( $test_function ) && function_exists ( $test_function )) <
$stat = $test_function ( $var );
$stat = ( $negate ) ? $stat ^ 1 : $stat ;
elseif( $test_function == ’empty’ ) <
$stat = empty( $var );
$stat = ( $negate ) ? $stat ^ 1 : $stat ;
elseif (! function_exists ( $test_function )) <
$stat = false ;
trigger_error ( » $test_function () is not a valid function» );
$stat = ( $stat ) ? true : false ;
return $stat ;
$a = » ;
$b = ’15’ ;

test_ref ( $a , ’empty’ , true ); //False
test_ref ( $a , ‘is_int’ ); //False
test_ref ( $a , ‘is_numeric’ ); //False
test_ref ( $b , ’empty’ , true ); //true
test_ref ( $b , ‘is_int’ ); //False
test_ref ( $b , ‘is_numeric’ ); //false
test_ref ( $unset , ‘is_numeric’ ); //false
test_ref ( $b , ‘is_number’ ); //returns false, with an error.

error_reporting() may give unexpected results if the @ error suppression directive is used.

@include ‘config.php’ ;
include ‘foo.bar’ ; // non-existent file

( 0 );

will throw an error level E_WARNING in relation to the non-existent file (depending of course on your configuration settings). If the suppressor is removed, this works as expected.

Alternatively using ini_set(‘display_errors’, 0) in config.php will achieve the same result. This is contrary to the note above which says that the two instructions are equivalent.

Only display php errors to the developer.

if( $_SERVER [ ‘REMOTE_ADDR’ ]== «» )
ini_set ( ‘display_errors’ , ‘On’ );
ini_set ( ‘display_errors’ , ‘Off’ );

Just replace with your ip address.

Creating a Custom Error Handler

function customError($errno, $errstr)
echo «Error: [$errno] $errstr
echo «Ending Script»;

In phpinfo() error reporting level display like a bit (such as 4095)

Maybe it is a simply method to understand what a level set on your host
if you are not have access to php.ini file

= ini_get ( ‘error_reporting’ );
while ( $bit > 0 ) <
for( $i = 0 , $n = 0 ; $i $bit ; $i = 1 * pow ( 2 , $n ), $n ++) <
$end = $i ;
$res [] = $end ;
$bit = $bit — $end ;

In $res you will have all constants of error reporting
$res[]=int(16) // E_CORE_ERROR
$res[]=int(8) // E_NOTICE


Оцените статью