I also installed Windows 7 on my computer and ran into the following problem:
I regularly run PHP scripts from the new command line, which now displays the following error message in a popup:
CLI no longer works.
I went to Google and tried most of the suggested ideas, but I still think this anger is tormenting me. Right now the product seems to show up regularly when I try to use file_get_contents () from a URL that points to an image file. Only comes up when the particular url is a protocol, http works fine for ftp files. There are other things that you learn by mistake.
This is PHP 5.3.0, which is distributed as xampp 1.7.2 .nada. All exe and dll have learned to copy via FAT32 and vice versa.
Not The Answer You’re Looking For? Browse Other Questions About The Windows 7 PHP Brand Or Ask Your Own Administrative Question.
PHP-CLI stops in the following cases: Windows 7 64 bit, PHP 5.6.8 64 bit only if Zend OpCache extension is actually editable !!!just php.ini and comment out zend_extension = php_opcache.dll (with ; in front)
If you receive this critical error after installing WAMP, it is very likely that your organization has another PHP installation installed on your primary computer. This may have been included in the Microsoft Web Platform Installer through other means. The first step you need to remove is PHP.
If that doesn’t work, killMake sure IIS and Apache are not trying to work on the same port. WAMP starts on the standard As port 80 and after that IIS will usually be the same. The easiest way to fix this is to disable IIS when connecting to WAMP, but you can install it with servers on port 81 or on an added port.
If that doesn’t work, my final thought. is to find multiple copies of the php.ini file on your computer. You can find places like the new Windows directory there. Just in case, make a backup copy of each file and then delete it from all folders, usually except the WAMP folder.
answered Jul 10 at 3:11 am
this happened to me when I said 5 in laravel. I have searched all over the place but did not find a solution that fixes my problem followed by debugging my web application in amazing places and found that if you briefly check your PHP code in the Laravel comments, about mod or blades, for example
answered Jun 12 15 at 15:33
11 22 bronze badges
I decided to ditch PHP 5.3.0 and go back to 5.2.11. As soon as I did that, the “CLI was stopped” problem disappeared.
answered Nov 10, 2009 6:56 PM
35.7k 1414 gold badges 7575 silver badges 8383 brown badges
I have the same problem with Windows 7 Professional.My Apache server just has no problem finding and running PHP on the best of the web, but the application’s command line performance is throwing the infamous “CLI has stopped working” message.The user account settings seem to passto execute it.Perl has no problem.
I always have to move my code to a coffee maker and run it there for debugging.
You didn’t say you were using xdebug, just in case I might be able to help. I have had this defect for a long time. The idea turned out that I am using a slightly weakened version of Xdebug (php_xdebug-2.2.0-5.4-vc9.dll). Replaces
I created a file with “php_xdebug-2.2.2-5.4-vc9.dll” and it magically made it work right away.
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
I am using Wamp and have updated both php.ini files (one needed for the cli, the other for normal use) with the last filename.”zend_extension = c: wamp bin php php5.4.3 ext php_xdebug-2.2.2-5.4-vc9.dll”
Then immediately put the following php file in the ext folder.
