Sometimes when trying to access your favourite website, Chrome may respond with "This page isn't working, if the problem continues please contact the site owner. HTTP error 400".  Therefore making it impossible to access the desired site from within Chrome's normal mode.

After getting to grips to angular, and getting so used to it's CLI; which helps accelerates some processes. it can be very weird when something working so consistently before suddenly. I experienced this error today when trying to generate a new component in my project.

If you are presently receiving this error, on your windows pc or Surface Pro book; fret not the fix is really simple and direct. The error reads:

" ... is unavailable, if the location is on this PC, make sure the device or drive is connected or the disc is inserted and then try again. If the location is on a network, make sure you're connected to the network or internet and then try again. If the location still can't be found, it might have been moved or deleted".

This can occur after you accidentally delete your previous Desktop location may be on your PC or one drive, or some effect of misconfiguration, virus or many other reasons. The simple fix is:

Solution:

1. Go to "This PC" or "My Computer" through start or pressing Window Key + E.
2. On the right / top section of the screen, look for Desktop and right-click it; then click on "Properties".
3. On the properties page, look for the "Location" tab.
4. In the "Location" the location tab, click on Restore default.

This can also affect Documents and other system drives, the fix is same for all.

Enjoy.

I recently just picked up MEAN.IO, and decided to work on my Windows machine today, Set up everything but one one thing, initialize a new MEAN project, gave me all the time "Prerequisite not installed: git". If you experience this too and have git installed already, don't beat up yourself so hard, it's a simple fix.

Ever experienced this error when installing MikText for using latex on windows. This was a weird one, given we ran the installation as admin and in an administrator privileged account yet the error kept given this error. The solution was very simple and direct.

You may have experienced this problem a couple of time, where your SD Card decides to go haywire on you and the only available option on your device is Erase Everything (Format). Here are some simple fixes that may help.


--- Advert ---

Internal SD Card Reader Available: 

Try with SD Lock off:

if your laptop has an internal SD Reader, there exist two quick fixes that usually works.
insert you SD-Card in an SD-Card Adapter, and see if Windows detects it, if Windows does. Follow the following steps.


The first step is to note the assigned drive letter; These can be seen from This PC / My Computer / Disk Management.

• Go to start, click on run (alternatively Window key + R) enter cmd.
• or type in Start, Command Prompt.
• Type chkdsk /f  /r /x driverletter: 
• i.e drive letter is the letter assigned to your drive. e.g if the letter e is assigned to your drive, then sample input may look like this:      chkdsk /f /r /x e:     

if your card is not detected or after detection, you cannot access it or get these error messages:

Cannot open volume for direct access 

The type of the file system is RAW.
CHKDSK is not available for RAW drives.

The type of the file system is FAT32.
Error in IOCTL call.

Then the below solution may help out.

Try with Write Lock on

Sometimes, trying your sdcard with write lock on does the magic, although you don't get to run a checkdisk on your sdcard, but you get the opportunity to backup your files before attempting the format option on your phone. (As at time of writing, I just had similar problem and this worked).

Just a nagging issue sometimes experienced in Android studio, when you can seem to build the app and all seems okay but build fails on "Configure Build" right after "Configure Settings". Restarting the IDE didn't fix it for me. Here was what fixed it in my case.

Here is the solution for those who get to run into this annoying restart loop, where you constantly get the BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (btfilter.sys) and sometime get a System_Service_Exception.

image from http://www.pcworld.com/article/2105785/acer-travelmate-pro-tmp645-mg-9419-review-this-mild-mannered-case-conceals-a-powerful-laptop.html

Hi! guys. Ever ran into that issue where you connect your Laptop to an external display, e.g TV; but AUDIO still comes from your Laptop's speaker. Half of the time a system restart fixes this, but just in case you restart and it doesn't still work, here are quick steps to get it fixed.

Some users may have been experiencing flickering issues when playing games. This can be particularly annoying and not occur in every game.

If you run into this error while trying to update your Xperia device using "Sony PC Companion", then PC companion is really having issues starting the Sony Mobile Update engine. The solution is a fairly simple one.

This error is a fairly new one, only recently surface on Windows 10; it is sometimes very similar to KERNEL_DATA_INPAGE_ERROR, have very similar symptoms. PCs on Windows 10 haven't been experiencing the KERNEL_DATA_INPAGE_ERROR but have been experiencing this, especially those that were formerly getting KERNEL_DATA_INPAGE_ERROR.

If during installation of the new Realtek Audio Driver, you are asked to restart, and after each restart you get the message about the install procedure which reads, (a) uninstall current driver restart (b) install driver, with the "next" button starting the uninstallation of the present driver, only to realise after restart, the same message comes up, over and over and over again (LOOP).

Ever felt that few seconds lag or freeze, after your back-light goes off due to inactivity, you hit a keyboard or your mouse and the screen shows black for a while, then suddenly flickers back on, and functions normally, but brings out a message.

Ever got that annoying message when installing an extension and Joomla  gives you the error message:

Many users have been having this critical error, and it seemed rather upsetting as it is barely less than a week since the release of the Windows 10 and a serious bug like this shows up. The full error reads:

Some users who accidentally interrupt their update (restart or shutdown), have been experiencing issues resuming the update, "Something happened error". The fix for this error is totally simple.