Recommended Posts

You may have noticed after upgrading to Windows 10, you can no longer access network shares.  You are 100% sure the login and password are correct but Windows is insisting your password is incorrect.  Or maybe you have disabled password protected sharing but it is still asking for a password.

 

This problem occurs when you have linked a Microsoft account to your login but have not setup (or you are not using) a homegroup.  

 

To see what is actually going on, let's look into the issue deeper.
 
In Windows 10, when a domain is not set and a Microsoft account is linked, it makes homegroup (tied to your Microsoft account) the default (and only) setting to use as authentication.   This causes incompatibility (both with Windows 10 and previous versions of Windows) if a homegroup is not used on the network.
 
In order to bypass this, we must "trick" Windows into thinking the network share is part of a domain.  By making Windows believe the share is part of a domain it will ignore homegroup authentication and use the legacy login system not tied to homegroups or Microsoft accounts.  

 

To do this, simply add <anything>\ to the login user name.    The <anything> can be whatever you please, it can be the PC Name, it can be WORKGROUP, it can be a period, it can even be Neowin if you want.  

 

Example:  Your User name is Bob, and your password is 12345.  You would log in as:

User:  .\Bob
Password: 12345


 Now, let's say you prefer the old insecure way of Windows shares and you have turned password protected sharing off.  (I am assuming you already know what you are doing and I will not cover how to do this or the dangers of doing so in this guide)

 

You would then login as the following:  

User:  .\Guest
Password:  <blank>


It remains to be seen whether this is a bug or by design.  If it is indeed a bug, it may one day be fixed and render this guide useless. (fair warning for everyone in the future)

 

 

Special thanks to warwagon and his original thread addressing this issue.

  • Like 2

OR you could just go into network setting and set it to use username and passwords to authenticate instead of a homegroup. The min issue then is merely to know what the actual windows username for your microsoft account is. 

5 hours ago, HawkMan said:

OR you could just go into network setting and set it to use username and passwords to authenticate instead of a homegroup. 

Except that doesn't actually do anything...

 

1.thumb.png.a25bd8b51892179ea23e6720b307

 

 

After adding .\  

Leads to:

3.thumb.png.02c4633306f4d843992e9f268c2e

 

 

 

 

I love how you started a new thread, the other was fine.

 

And just for the sake of this thread before buttman throws his 2 cents in - this method of logging onto a machine has been around for, I dunno, 10+ years? I've been doing it FOREVER. 

1 hour ago, Jared- said:

I love how you started a new thread, the other was fine.

 

And just for the sake of this thread before buttman throws his 2 cents in - this method of logging onto a machine has been around for, I dunno, 10+ years? I've been doing it FOREVER. 

I'm not even entirely sure this is the same issue as the other thread. especially since this focuses entirely on win10

  • 3 weeks later...

I too have been banging my head against the wall with this problem since upgrading both PCs on my home network from Windows 8.1 Pro to Windows 10 Pro yesterday. I should also highlight (as I believe it's rlevant to this issue) that at same time I changed the Windows login for BOTH PCs from local login to a Microsoft account. Prior to these changes I could access the network shares on my wife's PC by just entering username and password but today it just would not accept my password which I knew was correct.

A Google search toook me to this thread and after changing my username to format <computername>/Username it at last allowed me to connect to my wife's PC's shared folders. I registered on this forum solely to post my thanks for this.

1 hour ago, Circaflex said:

How is this thread any different than what warwagon created? 

 

The original thread by warwagon contained conflicting information and ended up turning into a debate rather than a guide.  It was confusing for anyone who came across it from searching.

 

The original thread by warwagon is credited and linked to as well in this guide.

  • 1 year later...

I am getting this error in a domain network and using a script to mapped a drive using net use command. When log in to Win 10 for the first time and run the script I am getting password error. Without entering any cred and close the command and rerun the script the error is gone and mapping the drive is successful. Would you know why I have to rerun before it work?

6 minutes ago, T0rqu3 said:

I am getting this error in a domain network and using a script to mapped a drive using net use command. When log in to Win 10 for the first time and run the script I am getting password error. Without entering any cred and close the command and rerun the script the error is gone and mapping the drive is successful. Would you know why I have to rerun before it work?

Try using Group Policy Preferences and item-level targetting (if required) instead of a script. It works without problems for us, has done for 2.5 years, across Windows 8.1 and Windows 10 machines.

 

Here is my configuration:

 

Group Policy > User Configuration > Preferences > Windows Settings > Drive Maps

 

Right click the blank white space > New > Mapped Drive

 

Set the following:

General Tab

Action = Replace

Location = Full FQDN of share

Drive Letter = Existing > Set letter from drop down list

Connect as (optional) = Leave blank unless the you have to use different credentials than the users' own (not recommended)

Hide/Show this drive = Choose your desired (it will determine whether it is visible in File Explorer

Hide/Show all drives = No Change

 

Common Tab

Stop processing items in this extension if an error occurs = unchecked

Run in logged-on user's security context (user policy option) = unchecked

Remove this item when it is no longer applied = checked

Item-level targetting = checked > Press the 'Targetting...' button to set your requirements.

 

Edited by Daedroth
  • Jason S. locked this topic
This topic is now closed to further replies.
  • Posts

    • Are you going to do performance benchmarks comparing all states? I'd be interested in seeing that in the next "part".
    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!