Error Path Busy 148 (0x94): How to Fix it

Running iisreset can fix this problem in most cases

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

ERROR_PATH_BUSY
XINSTALL BY CLICKING THE DOWNLOAD FILE
A message from our partner

For fixing Windows errors, we recommend Fortect:

Fortect will identify and deploy the correct fix for your Windows errors. Follow the 3 easy steps to get rid of Windows errors:

  • Download Fortect and install it on your PC
  • Launch the tool and Start scanning your PC for Windows errors
  • Right-click on Start Repair to deploy the right fix for each error encountered during the scan
Download Now Fortect has been downloaded by 0 readers this month, rated 4.6 on TrustPilot

Error_Path_Busy often comes with 148 (0x94) The path specified cannot be used at this time, and it usually affects developers. However, if you encounter it, there are a few ways to fix it.

How can I fix Error_Path_Busy?

Before trying anything else, ensure that your device is up to date with the latest patches and hotfixes.

1. Perform IISReset

  1. Press the Windows key + S and type cmd. Select Run as administrator.
    CMD elevated
  2. Next, run the iisreset command.
  3. Wait for the process to finish.

2. Restart Windows SharePoint Services Timer

  1. Press Windows key + R and type services.msc. Press Enter.
  2. Next, locate the Windows SharePoint Services Timer.
  3. Right-click it and choose Restart.

Alternatively, you can do this with Command Prompt:

  1. Open Command Prompt as administrator.
  2. Next, run the following commands:
    net stop SPTimerV4
    net start SPTimerV4
  3. Check if the problem is gone.

3. Recreate the Intepub directory

  1. Locate the Intepub directory.
  2. Rename it.
  3. Now recreate the directory.

As you can see, fixing Error_Path_Busy is simpler than you think, and in most cases, it can be solved by running a few commands.

This isn’t the only error, and we wrote about ERROR_BUSY_DRIVE and ERROR_NETWORK_BUSY in our previous guides, so don’t miss them for more information.

Our latest guide covers Error_Busy, another common error, so you might want to check it out.

More about the topics: error

User forum

0 messages