Fix the “Could not find this item. This is no longer located in [Path]. Verify the item’s location and try again”

 

This solution is more of a workaround but it gets the job done as a side-effect of another action. That being said, it’s perfect for users who don’t like using Command Prompt and who want to do everything using their mouse in a graphical environment. It’s also easy to use so make you try this one out!

1. Locate the problematic file or folder on your computer by navigating to it in the File Explorer. Right-click on it and choose the Add to archive option from the context menu.
2. When the archiving options window opens, locate the Delete files after archiving option and make sure you select it. Click OK to start the archiving process and, after it finishes, you should notice that your problematic file is missing!
3. Delete the archive you created as well by right-clicking on it and choosing the Delete option from the context menu.

Internet Explorer is not working properly insdide of a container when Mcafee is installed on the node

Symptoms Blank frame is displayed while viewing a javascript content via Internet Explorer . McAfee antivirus with Scriptscan feature is installed on the node. Cause Installation of McAfee AV with Scriptscan option replaces VBScript engine ...

Body

Symptoms

• Blank frame is displayed while viewing a javascript content via Internet Explorer .
• McAfee antivirus with Scriptscan feature is installed on the node.

Cause

Installation of McAfee AV with Scriptscan option replaces VBScript engine on the node and in containers from vbscript.dll:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
(default)    REG_SZ    C:\Windows\System32\vbscript.dll

to ScriptSn.20140523232758.dll

McAfee Scriptscan feature is not compatible with Virtuozzo Containers for Windows.

Resolution

McAfee Antivirus should be re-installed on the node without this feature. The following registry keys should be restored to original VBScript dlls in the existing containers:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
(default)    REG_SZ    C:\Windows\System32\vbscript.dll

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32
(Default)    REG_SZ    C:\Windows\System32\jscript.dll

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
(Default)    REG_SZ    C:\Windows\system32\vbscript.dll

HKEY_CLASSES_ROOT\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32
(Default)    REG_SZ    C:\Windows\System32\jscript.dll

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
(Default)    REG_SZ    C:\Windows\SysWOW64\vbscript.dll

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32
(Default)    REG_SZ    C:\Windows\SysWOW64\jscript.dll

Additional if the node has IE 9 is installed

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{16d51579-a30b-4c8b-a276-0ff4dc41e755}\InprocServer32
(Default)    REG_SZ    C:\Windows\System32\jscript9.dll

HKEY_CLASSES_ROOT\CLSID\{16d51579-a30b-4c8b-a276-0ff4dc41e755}\InprocServer32
(Default)    REG_SZ    C:\Windows\System32\jscript9.dll

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{16d51579-a30b-4c8b-a276-0ff4dc41e755}\InprocServer32
(Default)    REG_SZ    C:\Windows\SysWOW64\jscript9.dll

To reconfigure a container with default VBScript dlls the following command can be used:

vzctl CTID exec regsvr32 C:\Windows\System32\vbscript.dll
vzctl CTID exec regsvr32 C:\Windows\SysWOW64\vbscript.dll
vzctl CTID exec regsvr32 C:\Windows\System32\jscript.dll
vzctl CTID exec regsvr32 C:\Windows\SysWOW64\jscript.dll
vzctl CTID exec regsvr32 C:\Windows\System32\jscript9.dll
vzctl CTID exec regsvr32 C:\Windows\SysWOW64\jscript9.dll

In the example above, replace CTID with actual container ID number.

ASP 500 Error with Code 0x800700aa While browsing a .asp page

Problem :

Some times you try to browse a simple ASP page (Legacy ASP) hosted on IIS 7.5 or IIS 8.5 and you run in to following Error : 

Detailed Error Information 
Module IsapiModule 
Notification ExecuteRequestHandler 
Handler ASPClassic 
Error Code 0x800700aa 
Requested URL http://localhost/New_Site/Default.asp 
Physical Path C:\inetpub\wwwroot\New_Site\Default.asp 
Logon Method Anonymous 
Logon User Anonymous

You try all the other options like Enabling 32 Bit, Changing AppPool Pipeline mode to Classic, installing .net framework 1.1 or 2.0 but it doesn't help. 

Diagnose the Problem : 

 To find the main reason of this problem you will need to run Process Monitor and filter the logs to see only ProcMon Logs related to w3Wp.exe. 

While digging the logs, you may find some logs similar to following : 

12:31:49.0797868 PM    w3wp.exe    8264    CreateFile    C:\Program Files\McAfee\VirusScan\scriptsn.dll    PATH NOT FOUND 

                                                                         OR

12:31:49.0797868 PM    w3wp.exe    8264    CreateFile    C:\Program Files\McAfee\VirusScan\scriptsn.dll    PATH NOT FOUND  

Now the question is, why an asp file request is calling a .dll file which is related to to AntiVirus program.

Some times , when AntiVirus program is installed on your server or Updated , it add this DLL as part of there ScriptScan feature  to intercept the script calls before they are executed on following Regresty Key : 

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 
    (Default)    REG_SZ    C:\Program Files\McAfee\VirusScan\scriptsn.dll

In normal Conditions, this Registry Key (CLSID - HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 ) points to VBScript.dll but here it is pointing to C:\Program Files\McAfee\VirusScan\scriptsn.dll. And this is the reason, ASP files are not being

 processed when requested.

After you successfully remove VSE, the system reports the following error:

The VBscript engine does not run any scripts on this machine
Some applications that utilize java script may not run properly

Procmon shows that when a VBScript is executed on this server, instead of calling the VBScript Driver vbscript.dll, it continues to call the McAfee driver from:

c:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.20110315093749.dll

Applet logs record the following errors related to VBScript after you use MFERemoval100.exe to remove VSE:

<Part of Applet--2016.12.21--09.58.01--[MFERemoval100.exe].txt>
E  Failed to set HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 to C: \windows\SysWOW64\vbscript.dll
S  C:\windows\SysWOW64\vbscript.dll was register.
E  Failed to set HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 to C:\windows\system32\vbscript.dll
S  C:\windows\system32\vbscript.dll was register.
S  HKEY_LOCAL_MACHINE\Wow6432Node\SOFTWARE\Classes\VBScript deleted.

Solution

Revert the registry key to its default value:

CAUTION: This article contains information about opening or modifying the registry.

• The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
• Before proceeding, Technical Support strongly recommends that you back up your registry and understand the restore process. For more information, see: http://support.microsoft.com/kb/256986.
• Do not run a REG file that is not confirmed to be a genuine registry import file.

1. Press Windows+R, type regedit, and click OK.
2. Navigate to the following registry key:
   
   HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
3. Right-click the registry key and select Permissions.
4. Select Administrators and give Full Control.
   
   NOTE: In some instances, you might have to change ownership to change the permissions for these registry keys. Click Advanced Sharing, Change, and then change the permissions from the System account to the Admin account.
    
5. Replace the following string value: 
   C:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.nnnnnnnnnnn.dl
   
   With:
   C:\Windows\System32\vbscript.dll
    
6. Navigate to the following registry key:
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32]
    
7. Replace the following string value:
   C:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.nnnnnnnnnnn.dl
   With:
   C:\Windows\System32\jscript.dll
8. (64-bit systems only) Navigate to the following registry key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
9. Replace the following string value:
   C:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.nnnnnnnnnnn.dl
   With:
   C:\Windows\System32\vbscript.dll
10. (64-bit systems only) Navigate to the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}\InprocServer32
11. Replace the following string value:
    C:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.nnnnnnnnnnn.dl
    With:
    C:\Windows\SysWOW64\jscript.dll
     
12. Register vbscript.dll. At an elevated command prompt, type the following and press ENTER:
    
    c:\windows\system32\regsvr32.exe vbscript.dll
     
13. Register jscript.dll. At an elevated command prompt, type the following and press ENTER:
    
    c:\windows\system32\regsvr32.exe jscript.dll

Backup and restoring websites on the Internet Information Services (IIS) Manage

To back up and restore IIS 6:

1. Open the IIS Manager.
2. Right-click the machine labeled as Local Computer.
3. Click All Tasks > Backup/Restore Configuration > Create Backup.
   
4. Type a name for the backed up configuration and then click OK.
   
5. Click Close.
6. Open the %windir%\system32\inetsrv\MetaBack directory and copy the created backup to a local folder.
   
7. Reinstall IIS.
8. Open the local folder and copy the backup file to the %windir%\system32\inetsrv\MetaBack directory.
9. Open the IIS Manager.
10. Right-click the machine labeled as Local computer.
11. Click All Tasks > Backup/Restore Configuration.
12. Select the backup name and then click Restore > Yes > OK.
13. Click Close.

To back up and restore IIS 7 or IIS 8:

1. Open cmd.exe.
2. Navigate to %windir%\system32\inetsrv\.
3. Execute following command to back up configuration:
   appcmd.exe add backup <backupname>.
4. Open the %windir%\system32\inetsrv\backup directory and copy the backup folder to a local folder.
5. Reinstall IIS.
6. Open the local folder and copy the backup folder to the %windir%\system32\inetsrv\backup directory.
7. Execute following command to back up configuration:
   appcmd.exe restore backup <backupname>
   
   

 

Copy and Paste is not working on my Remote Desktop Connection

when clipboard stops working?

 

1. Load up task manager (right click taskbar and select Task Manager)
2. Go to the Processes Tab
3. Select rdpclip.exe
4. Click End Process
5. Go to the Application Tab
6. Click New Process
7. Type rdpclip
8. Click Ok

 

Show/Hide Security Tab in Windows 10

Using Windows Registry

Open the registry of your system by typing “regedit.exe" in Run window. And go to following directory
HKEY_CURRENT_USER\Software\Microsoft\Windows\Currentversion\Policies\Explorer

When you open it, in right window you’ll see the “NoSecurityTab" change its value to 1 by modifying it. And refresh your window. And here you go. Security tabs from each folder will hide from every one.

Whenever you want to show it again, again go to same registry path and set its value to 0 again, the security tab will be visible again.

Using Group Policy Editor

You can also show/hide “Security" tab through Group Policy editor. Open the “Local Group Policy editor" by writing it in Start Menu. Then open the first result it gives you on typing.
Now open the User Configuration\Administrative Tools\Windows Components\File Explorer and double click on it, now open Remove Security Tab from right hand side window.

When you open “Remove Security Tab", there is 3 options: not configured, enable and disable.
If you want to remove Security Tab, select the “enable" and if don’t then press on “disable".

After selecting any option press “OK" and your settings will be changed. This is another easy and simple way to hide/show Security tab.

Using command line

Giving specific commands on Command Line Window can also enable or disable the “Security" tab.
Following are commands for enabling and disabling the “Security" tab.

Enable Security Tab

REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer /v Nosecuritytab /t REG_DWORD /d 0 /f

Disable Security Tab

REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer /v Nosecuritytab /t REG_DWORD /d 1 /f

After entering your required command, press enter and close the CMD and you are done with enabling or disabling the Security Tab.
Above three are easy and simple ways for your problem of enabling or disabling the Security Tab. You can go for anyone of them. All are simple and reliable ways.

Windows 10 Start menu not working after joined to Domain

here may be many scenarios this could happen.  in this scenario you may be having a Windows 2008 R2 domain controller with this kind of group policy setting for registry (this is not a default group policy setting)


And These are the Default Permissions for this Registry Entry


The problem is For windows 10 “CLASSES_ROOT” need more permission to Access Windows Start menu settings
With Windows 2008 R2 Domain controllers this permission group is not available.If you need to add customized group policy settings for “CLASSES_ROOT” you need to have Windows 2012 R2 Domain controller or server 2016 domain Controller in your environment.

This is a screen shot from default settings for “CLASSES_ROOT” in Server 2016 Domain controller



What happen is When you modify that Registry entry with a Group policy in Windows 2008 R2 domain controller.Windows 10 Client PC will loss “ALL APPLICATION PACKAGES” FROM reading CLASSES_ROOT Registry permissions.
If your having only Windows 2008 R2 domain controller.
Delete This Group policy setting
Computer configuration > policies > Windows settings > Security Settings > registry > “CLASSES_ROOT”
run “gpupdate /force” on windows 10 Client PC
Login to Windows 10 PC As Domain Administrator
Go to Registry (Press Windows key + R and type regedit and press enter)
right click HKEY_CLASSES_ROOT And click permission and add “ALL APPLICATION PACKAGES” Group from LOCAL computer and give read only permission

Then click “Advanced” Button and tick “Replace all child object permission entire with inheritable permission entries from the object” and click apply it might take some time to apply settings.click OK and close registry editor and reboot.
If you have  introduced a 2012 R2 or a Server 2016 Domain controller to the existing domain with 2008 R2 you can just edit the Group policy setting for CLASSES_ROOT From 2012 R2 Domain controller Group policy editor and edit CLASSES_ROOT and click on “Add” Button > click “Location” Button > Select “LOCAL COMPUTER NAME” and Click OK.
Click “Advanced” And click “Find” then Select “ALL APPLICATION PACKAGES” Group click OK Twice and give “Read only” permissions for “ALL APPLICATION PACKAGES” Group.Click OK to save. run a “gpupdate /force” on the client computer and reboot.
that’s it, hope this will help to fix start menu not working problem in windows 10 ,even if your not in a domain environment you can just check this registry entry for correct permissions.