Super Safe Double Padded Korean Face Mask!!!

Make Windows 10 Accept File Paths Over 260 Characters

How to Make Windows 10 Accept File Paths Over 260 Characters

With the Anniversary Update of Windows 10, you can finally abandon the 260 character maximum path limit in Windows. You just need to make a minor edit to the Windows Registry or Group Policy. Here’s how to make it happen.

Before Windows 95, Windows only allowed file names that were eight characters long, with a three character file extension–commonly known as an 8.3 filename. Windows 95 abandoned that to allow long file names, but still limited the maximum path length (which includes the full folder path and the file name) to 260 characters. That limit has been in place ever since. If you’ve ever run into this limit, most likely it was when you were trying to copy deep folder structures into other folders, such as when copying the contents of a hard drive to a folder on another drive. The Windows 10 Anniversary Update finally adds the option to abandon that maximum path length.

There is one caveat. This new setting won’t necessarily work with every application out there, but it will work with most. Specifically, any modern applications should be fine, as should all 64-bit applications. Older 32-bit applications need to be manifested in order to work, which really just means that the developer has indicated in the application’s manifest file that the application supports longer paths. Most popular 32-bit apps should experience no problem. Still, you don’t risk anything by trying the setting out. If an application doesn’t work, the only thing that will happen is that it won’t be able to open or save files that are saved in places where the full path exceeds 260 characters.

Home Users: Remove the 260 Character Path Limit by Editing the Registry

If you have a Windows Home edition, you will have to edit the Windows Registry to make these changes. You can also do it this way if you have Windows Pro or Enterprise, but feel more comfortable working in the Registry than Group Policy Editor. (If you have Pro or Enterprise, though, we recommend using the easier Group Policy Editor, as described in the next section.)

To get started, open the Registry Editor by hitting Start and typing “regedit.” Press Enter to open Registry Editor and give it permission to make changes to your PC.

In the Registry Editor, use the left sidebar to navigate to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

On the right, find a value named LongPathsEnabled and double-click it. If you don’t see the value listed, you’ll need to create it by right-clicking the FileSystem key, choosing New > DWORD (32-bit) Value, and then naming the new value LongPathsEnabled .

In the value’s properties window, change the value from 0 to 1 in the “Value data” box and then click OK.

You can now close Registry Editor and restart your computer (or sign out of your account and sign back on). If you ever want to reverse the changes, just head back to the LongPathsEnabled value and set it from 1 back to 0.

Pro and Enterprise Users: Remove the 260 Character Path Limit with the Local Group Policy Editor

If you’re using Windows 10 Pro or Enterprise, the easiest way to disable the new app install notifications is by using the Local Group Policy Editor. It’s a pretty powerful tool, so if you’ve never used it before, it’s worth taking some time to learn what it can do. Also, if you’re on a company network, do everyone a favor and check with your admin first. If your work computer is part of a domain, it’s also likely that it’s part of a domain group policy that will supersede the local group policy, anyway.

In Windows 10 Pro or Enterprise, hit Start, type gpedit.msc, and press Enter.

In the Local Group Policy Editor, in the left-hand pane, drill down to Computer Configuration > Administrative Templates > System > Filesystem. On the right, find the “Enable win32 long paths” item and double-click it.

In the properties window that opens, select the “Enabled” option and then click “OK.”

You can now exit the Local Group Policy Editor and restart your computer (or sign out and back in) to allow the changes to finish. If at any time you want to reverse the changes, just follow the same procedure and set that option back to “Disabled” or “Not Configured.”

The maximum path limit may not be something you’ve ever run into, but for some people it can certainly be the occasional frustration. Windows 10 has finally added the ability to remove that limit. You just have to make a quick change to the Registry or Group Policy to make it happen.

Bolt man chasing a nut woman

Virtual machines automatic startup with VMware Workstation

By using “share” feature on your existing virtual machines, or by creating a new one in folder “Shared VMs”, you will be able to use option to automatically start virtual machines when host computer starts. That way you can have small office server virtualized infrastructure based on VMware Workstation software.

1. To enable start virtual machine with host computer, you need to “right click” on existing virtual machine and select “manage>share” option

2.  After that, you will be presented with “Share VM Wizard“, so just click “Next“.

3.  On this dialog, you can chose whether you just want to enable “shared” for existing virtual machine, or you want to create a clone of existing machine to run as shared virtual machine. “Move the virtual machine” will move all existing data files of selected virtual machine to predefined “Shared Virtual Machines” folder.

4.  VMware Workstation will process your request, and when finished, selected virtual machine will appear in “Shared VMs” folder.

5.  After selecting “Shared VMs” folder in Library column, you will need to click on “Manage AutoStart VMs” and select virtual machines which will start with host computer. Also, if you start multiple virtual machine, you should define delayed start between each virtual machine, to reduce impact on hosts disk and CPU resources.

Cleaning up Network Connections in Windows 7

Windows makes a mess of all the network adapters when installing NIC cards. Sometimes, you remove network adapters, and you're left with something like "Local Area Network 3" that can't be renamed back to "Local Area Network". The problem is, Windows remembers the previous adapter (even if it is physically removed), so you can't rename the adapter, otherwise it would conflict with previously named adapters. 

To view and remove all previously (non-connected) NIC adapters:
1. Open cmd.
2. Type 
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
3. Open device manager by running devmgmt.msc.
4. View > Show Hidden Devices.

Now, you can remove any adapters that were previously installed (but no longer present) in windows. These are the adapters that appear slightly grayed out in Device Manager.


After doing so, you should now be able to rename the network adapters back to "Local Area Connection".

Create more than 4 Network Cards in Virtualbox

Create more than 4 Network Adapters in Virtualbox

I've seen this post from - https://www.eanderalx.org/virtualization/8_network_card_vbox. I re-posted it here on my blog for reference purposes, so that I don't have to search for it the next time I need it.

Virtualbox supports up to eight network cards. If you look into the *.vbox you will see that there are already preconfigured but disabled. Unfortunately inside the VBox GUI we could only configure up to four. I will show how to get and configure the other.

You have to use VBoxManage to get the other network cards. After the option will always be the NIC Number count one to eight. Here I will use five and the name of the machine that will be configured is “network-test”.

Set Mode and enable NIC

When a Mode is set the NIC will be enabled.

1. Set NIC five to Host-Only Mode and User vboxnet0 (Initially existing Host-Only Net)
   

   VBoxManage modifyvm network-test --nic5 hostonly
   VBoxManage modifyvm network-test --hostonlyadapter5 "vboxnet0"

2. Set NIC five to Bridge eth1
   

   VBoxManage modifyvm network-test --nic5 bridged
   VBoxManage modifyvm network-test --bridgeadapter5 "eth1'

   NOTE: In Windows, use the actual Network Adapter Name instead of eth1

3. Set NIC to NAT Mode
   

   VBoxManage modifyvm network-test --nic5 nat

4. Use the internal VM net “test01”
   

   VBoxManage modifyvm network-test --nic5 intnet
   VBoxManage modifyvm network-test --intnet5 "test01"

Configuring NIC

• To use VLAN and some other things in VMs the Promiscuous mode have to be enabled
  

  VBoxManage modifyvm network-test --nicpromisc5 allow-all

• Use other hardware type (Intel Pro/1000 MT Server)
  

  VBoxManage modifyvm network-test --nictype5 82545EM

• Dis/connect cable
  

  VBoxManage modifyvm network-test --cableconnected5 off

All Options

The help of VBoxManage contains much more options than I've showed

Can't create a file in drive C's root directory - Windows 8/8.1

Can't create a file in drive C's root directory - Windows 8/8.1

Have you ever experienced your Windows 8/8.1 computer prompting you that you do not have permissions on some folders especially on C drive's root directory even if you're an administrator and have disabled User Account Control?

Solution

In Windows 7 or 8, users (even administrators) are not allowed to create files in the C drive root directory, an error message like “A required privilege is not held by the client” or “access is denied” will be prompted.

To fix this, just turn off the User Account Control (UAC). In Windows 8, do not turn off the UAC via control panel, you must go through the registry.

1. Press “Windows Key + R”, type regedit
2. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA
3. Update the EnableLUA value to 0 (turn if off)
4. Restart Windows.

Here's the story I got from Microsoft:

1. Microsoft prefers that we leave UAC enabled.
2. If we do choose to disable UAC via the registry, then we must also disable the 'luafv' service as well to stop the UAC File virtualization service errors.

How to disable luafv service

1. HKLM\System\CurrnetControlSet\Services\luafv
2. Set the value of "Start" to 4.
3. Reboot the server. 

Ramifications of disabling luafv

1. You will lose IE sandbox
2. Modern apps (metro) will not work
3. "There is no way we can predict all side effects, but the above two components will surely be affected"
4. http://support.microsoft.com/kb/2526083/en-us