<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[An article has been published[1] explaining how to prevent #Chrome from downloading the #Gemini Nano model on #Windows via a Registry change.]]></title><description><![CDATA[<p>An article has been published[1] explaining how to prevent <a href="https://dragonscave.space/tags/Chrome" rel="tag">#<span>Chrome</span></a> from downloading the <a href="https://dragonscave.space/tags/Gemini" rel="tag">#<span>Gemini</span></a> Nano model on <a href="https://dragonscave.space/tags/Windows" rel="tag">#<span>Windows</span></a> via a Registry change.  But it seems to me that such a method is only effective for as long as Google respects that policy in the Registry, doesn't change its name/path, etc.</p><p>Instead, has anybody tried creating an empty weights.bin file in the relevant location[2], and then removing all permissions from that file so that Chrome can't read, write, replace, or do anything else with it?</p><p>[1] <a href="https://pureinfotech.com/stop-chrome-gemini-nano-download-windows-11/" rel="nofollow noopener"><span>https://</span><span>pureinfotech.com/stop-chrome-g</span><span>emini-nano-download-windows-11/</span></a></p><p>[2] %LOCALAPPDATA%\Google\Chrome\User Data\OptGuideOnDeviceModel</p><p><a href="https://dragonscave.space/tags/AI" rel="tag">#<span>AI</span></a> <a href="https://dragonscave.space/tags/LLM" rel="tag">#<span>LLM</span></a> <a href="https://dragonscave.space/tags/LLMs" rel="tag">#<span>LLMs</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/be3ff108-dabb-45c1-a127-1fac4cf32dc9/an-article-has-been-published-1-explaining-how-to-prevent-chrome-from-downloading-the-gemini-nano-model-on-windows-via-a-registry-change.</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 21:39:03 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/be3ff108-dabb-45c1-a127-1fac4cf32dc9.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 07 May 2026 15:49:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to An article has been published[1] explaining how to prevent #Chrome from downloading the #Gemini Nano model on #Windows via a Registry change. on Thu, 07 May 2026 15:55:56 GMT]]></title><description><![CDATA[<p>So, probably do the Registry thing as well.</p>]]></description><link>https://board.circlewithadot.net/post/https://dragonscave.space/users/jscholes/statuses/116534106933022199</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://dragonscave.space/users/jscholes/statuses/116534106933022199</guid><dc:creator><![CDATA[jscholes@dragonscave.space]]></dc:creator><pubDate>Thu, 07 May 2026 15:55:56 GMT</pubDate></item><item><title><![CDATA[Reply to An article has been published[1] explaining how to prevent #Chrome from downloading the #Gemini Nano model on #Windows via a Registry change. on Thu, 07 May 2026 15:55:37 GMT]]></title><description><![CDATA[<p>I just did this on my own machine which hadn't received the unwanted download yet.  I also revoked all permissions on the "OptGuideOnDeviceModel" folder, preventing its contents from even being enumerated.</p><p>That said: as Chrome hadn't downloaded the file in the first place, it's impossible to tell whether this is a sound solution or not.  The continued absence of the model file isn't really evidence.</p><p>And, Google could just change where they store it anyway.</p>]]></description><link>https://board.circlewithadot.net/post/https://dragonscave.space/users/jscholes/statuses/116534105714997766</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://dragonscave.space/users/jscholes/statuses/116534105714997766</guid><dc:creator><![CDATA[jscholes@dragonscave.space]]></dc:creator><pubDate>Thu, 07 May 2026 15:55:37 GMT</pubDate></item></channel></rss>