<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	 xmlns:media="http://search.yahoo.com/mrss/" 
	>
<channel>
	<title>
	Comments on: Enable SMB 1.0/CIFS File Sharing Support in Windows 11	</title>
	<atom:link href="https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/feed/" rel="self" type="application/rss+xml" />
	<link>https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/</link>
	<description>Windows Insides</description>
	<lastBuildDate>Wed, 08 Apr 2026 04:24:04 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Leonie		</title>
		<link>https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/#comment-2090</link>

		<dc:creator><![CDATA[Leonie]]></dc:creator>
		<pubDate>Thu, 10 Jul 2025 09:19:02 +0000</pubDate>
		<guid isPermaLink="false">https://winsides.com/?p=415#comment-2090</guid>

					<description><![CDATA[Good shout&lt;a href=&quot;https://www.morningstar.com/news/globe-newswire/9489727/area-52-named-1-best-thc-gummies-by-oregon-observer&quot; rel=&quot;nofollow ugc&quot;&gt;.&lt;/a&gt;]]></description>
			<content:encoded><![CDATA[<p>Good shout<a href="https://www.morningstar.com/news/globe-newswire/9489727/area-52-named-1-best-thc-gummies-by-oregon-observer" rel="nofollow ugc">.</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Vigneshwaran		</title>
		<link>https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/#comment-120</link>

		<dc:creator><![CDATA[Vigneshwaran]]></dc:creator>
		<pubDate>Fri, 16 Aug 2024 12:23:12 +0000</pubDate>
		<guid isPermaLink="false">https://winsides.com/?p=415#comment-120</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/#comment-119&quot;&gt;Erdinc Hocalar&lt;/a&gt;.

Hi Mr. Erdinc Hocalar,

Thank you for reaching out! It’s absolutely okay to share your issue related to Windows 10 here, and we truly appreciate you taking the time to explain your situation. We’re here to help with all Windows-related concerns, whether it’s Windows 10 or Windows 11, so you’re in the right place!

We understand that you&#039;re experiencing an issue where your NAS setup is accessible on full Windows 10 devices but not on those running Windows 10 Tiny 21H2, despite the network drive being visible.

&lt;strong&gt;Possible Causes:&lt;/strong&gt;

- Missing network components  
- Different security settings  
- Disabled SMB/CIFS support  
- Credential issues  
- Local policy restrictions


&lt;strong&gt;Possible Solutions:&lt;/strong&gt;&lt;br&gt;
&lt;em&gt;Check Local Security Policies&lt;/em&gt;: Windows 10 Tiny might have stricter local security policies. You can adjust these by opening the Local Security Policy editor (secpol.msc), where you can review and modify settings that might be blocking access to the NAS.
&lt;br&gt;
&lt;em&gt;Adjust Security Settings:&lt;/em&gt; The security settings on Windows 10 Tiny might be more restrictive, leading to access issues. Ensure that network discovery and file sharing are enabled in Control Panel &gt; Network and Sharing Center &gt; Advanced sharing settings. If password-protected sharing is on, make sure your NAS credentials are correctly configured.
&lt;br&gt;
&lt;em&gt;Manage Credentials:&lt;/em&gt; Credentials might not be properly handled by Windows 10 Tiny. Open the Credential Manager and manually add your NAS credentials. This ensures that the correct username and password are used when accessing the NAS.
&lt;br&gt;
&lt;em&gt;Check for Missing Network Components:&lt;/em&gt; Since Windows 10 Tiny is a minimal version, it might be missing certain networking features that are necessary for proper NAS access. These could include things like file sharing services or network protocols that are usually present in the full version.
To check for missing components, you may need to compare the installed features on your Windows 10 Tiny device with those on a full Windows 10 version. Unfortunately, if critical networking features are absent, you might need to install them manually or consider using the full version of Windows for these tasks.
&lt;br&gt;
&lt;em&gt;Enable SMB/CIFS File Sharing Support:&lt;/em&gt; You might already be aware of enabling SMB/CIFS support from the post, but it’s worth listing it here as a possible solution. Ensure that SMB 1.0/CIFS File Sharing Support is enabled on your Windows 10 Tiny device.&lt;br&gt;

We hope the above solutions help resolve your issue. If the problem persists, please let us know, and we’ll do our best to find additional solutions to assist you. Thank you for visiting Winsides.com

Best Regards
Vigneshwaran]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/#comment-119">Erdinc Hocalar</a>.</p>
<p>Hi Mr. Erdinc Hocalar,</p>
<p>Thank you for reaching out! It’s absolutely okay to share your issue related to Windows 10 here, and we truly appreciate you taking the time to explain your situation. We’re here to help with all Windows-related concerns, whether it’s Windows 10 or Windows 11, so you’re in the right place!</p>
<p>We understand that you&#8217;re experiencing an issue where your NAS setup is accessible on full Windows 10 devices but not on those running Windows 10 Tiny 21H2, despite the network drive being visible.</p>
<p><strong>Possible Causes:</strong></p>
<p>&#8211; Missing network components<br />
&#8211; Different security settings<br />
&#8211; Disabled SMB/CIFS support<br />
&#8211; Credential issues<br />
&#8211; Local policy restrictions</p>
<p><strong>Possible Solutions:</strong><br />
<em>Check Local Security Policies</em>: Windows 10 Tiny might have stricter local security policies. You can adjust these by opening the Local Security Policy editor (secpol.msc), where you can review and modify settings that might be blocking access to the NAS.<br />
<br />
<em>Adjust Security Settings:</em> The security settings on Windows 10 Tiny might be more restrictive, leading to access issues. Ensure that network discovery and file sharing are enabled in Control Panel > Network and Sharing Center > Advanced sharing settings. If password-protected sharing is on, make sure your NAS credentials are correctly configured.<br />
<br />
<em>Manage Credentials:</em> Credentials might not be properly handled by Windows 10 Tiny. Open the Credential Manager and manually add your NAS credentials. This ensures that the correct username and password are used when accessing the NAS.<br />
<br />
<em>Check for Missing Network Components:</em> Since Windows 10 Tiny is a minimal version, it might be missing certain networking features that are necessary for proper NAS access. These could include things like file sharing services or network protocols that are usually present in the full version.<br />
To check for missing components, you may need to compare the installed features on your Windows 10 Tiny device with those on a full Windows 10 version. Unfortunately, if critical networking features are absent, you might need to install them manually or consider using the full version of Windows for these tasks.<br />
<br />
<em>Enable SMB/CIFS File Sharing Support:</em> You might already be aware of enabling SMB/CIFS support from the post, but it’s worth listing it here as a possible solution. Ensure that SMB 1.0/CIFS File Sharing Support is enabled on your Windows 10 Tiny device.</p>
<p>We hope the above solutions help resolve your issue. If the problem persists, please let us know, and we’ll do our best to find additional solutions to assist you. Thank you for visiting Winsides.com</p>
<p>Best Regards<br />
Vigneshwaran</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Erdinc Hocalar		</title>
		<link>https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/#comment-119</link>

		<dc:creator><![CDATA[Erdinc Hocalar]]></dc:creator>
		<pubDate>Wed, 14 Aug 2024 20:22:15 +0000</pubDate>
		<guid isPermaLink="false">https://winsides.com/?p=415#comment-119</guid>

					<description><![CDATA[Hi Vigneshwaran,

My problem is quite similar but with Windows 10. I hope this is not an issue posting my question in a windows 11 tutorial.
I&#039;m experimenting with Rasberry Pi5 and OpenMediaVault, I&#039;ve set up a NAS with 4 X 4TB SSD drives. The SSD drives are combined in one (snapraid) pool. I have multiple laptops and desktops all on the Windows 10 operating system. The machines running Windows 10 full version have no problem accessing the network drive. But on the machines running Windows 10 Tiny 21H2 the network drive is visible but access is denied. All the machines are visible to each other and can access each other&#039;s drive. On the machines running on Windows 10 Tiny I&#039;m logged in with a local account, not with my Microsoft account.
Logging in with my Microsoft account instead of my local account didn&#039;t make any difference.
I hope you can solve my problem,

Kind regards,

Erdinç]]></description>
			<content:encoded><![CDATA[<p>Hi Vigneshwaran,</p>
<p>My problem is quite similar but with Windows 10. I hope this is not an issue posting my question in a windows 11 tutorial.<br />
I&#8217;m experimenting with Rasberry Pi5 and OpenMediaVault, I&#8217;ve set up a NAS with 4 X 4TB SSD drives. The SSD drives are combined in one (snapraid) pool. I have multiple laptops and desktops all on the Windows 10 operating system. The machines running Windows 10 full version have no problem accessing the network drive. But on the machines running Windows 10 Tiny 21H2 the network drive is visible but access is denied. All the machines are visible to each other and can access each other&#8217;s drive. On the machines running on Windows 10 Tiny I&#8217;m logged in with a local account, not with my Microsoft account.<br />
Logging in with my Microsoft account instead of my local account didn&#8217;t make any difference.<br />
I hope you can solve my problem,</p>
<p>Kind regards,</p>
<p>Erdinç</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
