Recommended Posts

Hey all, I just noticed something today, whenever I search something on Google, I always get results in Texas. So I decided to open up Google Maps, and learn the browser access my location, and it showed that I was in Texas.

 

Anyone know what might be causing this issue? I did the test on my iPhone that is connected to the same wifi, but I'm not having any issues there. 

Try to clear cache and cookies and see your whether you are logged in as Google account when you tried on Google Map and also try some geolocation site to confirm location for cross reference.

Why would you want google to know where you are?

Okay, I don't think you're really understanding my question. I don't really care where Google knows where I'm at, I stated that I was using GOOGLE'S BROWSER, Chrome. 

 

Anyway.

 
I tried that iplocation website someone posted above, and it said that I was in my current hometown in California, so that should mean things are fine on my end right? But for example, I went to a redbox locator website, and it still pointed me to Dallas. So something still isn't configured... I was using a VPN for about a month for a game, but I've removed it. 

 

Okay, I don't think you're really understanding my question. I don't really care where Google knows where I'm at, I stated that I was using GOOGLE'S BROWSER, Chrome. 

 

Anyway.

 
I tried that iplocation website someone posted above, and it said that I was in my current hometown in California, so that should mean things are fine on my end right? But for example, I went to a redbox locator website, and it still pointed me to Dallas. So something still isn't configured... I was using a VPN for about a month for a game, but I've removed it. 

 

 

 

All Google's services are tied up together so the response is spot-on that you should check where Google things you are.

 

Try the solution before getting on your high horse.

He's right though, the question "why would you want Google to know where you are?" is irrelevant to the topic.

Have you tried ChuckFinley's suggestion? What happens if you use Google with a different browser, does it still think that you're in a different state? I assume it would, but it's always best to be sure.

All Google's services are tied up together so the response is spot-on that you should check where Google things you are.

 

Try the solution before getting on your high horse.

 

Can we please keep the irrelevant responses out of this thread? 

 

He's right though, the question "why would you want Google to know where you are?" is irrelevant to the topic.

Have you tried ChuckFinley's suggestion? What happens if you use Google with a different browser, does it still think that you're in a different state? I assume it would, but it's always best to be sure.

 

Yeah I've changed my location from the search bar manually to my zipcode, but whenever I do "auto locate" or whatever it is, I still get pointed back to Dallas, TX. I've tried Firefox, and I'm not sure if it's just a Google thing, becuase if I go to any website that requests my location, let's say Redbox, LA Fitness, etc, they all point me back locations near Dallas. 

 

I am assuming it was a VPN that I used (wtfast) in the past, but I've removed that, and restarted since then. I'll try clearing my cache, and seeing if that does anything. But that IP locator website that was posted above has my current location correct, so I'm not sure what the problem is..

Can we please keep the irrelevant responses out of this thread? 

 

 

Yeah I've changed my location from the search bar manually to my zipcode, but whenever I do "auto locate" or whatever it is, I still get pointed back to Dallas, TX. I've tried Firefox, and I'm not sure if it's just a Google thing, becuase if I go to any website that requests my location, let's say Redbox, LA Fitness, etc, they all point me back locations near Dallas. 

 

I am assuming it was a VPN that I used (wtfast) in the past, but I've removed that, and restarted since then. I'll try clearing my cache, and seeing if that does anything. But that IP locator website that was posted above has my current location correct, so I'm not sure what the problem is..

 

The IP locators use a database of locations that tally to IP addresses and lookup the location from your IP.  Given Firefox says you're also in Dallas, TX it would seem that a database somewhere is wrong for your IP.  Do you get consistent results from IP locators online or do some of those also point to you being in Dallas, TX?

The IP locators use a database of locations that tally to IP addresses and lookup the location from your IP.  Given Firefox says you're also in Dallas, TX it would seem that a database somewhere is wrong for your IP.  Do you get consistent results from IP locators online or do some of those also point to you being in Dallas, TX?

 

Well I just went to Target.com on my iPhone and did a "Search for store by current location" and it was able to find me stores in my current location, so I'm starting to think it might be something with my PC settings or something? 

  • 6 months later...

Try navigating to chrome://net-internals/#dns then choose Clear host cache

 

Thanks. I know this is a little late, but I still had the issue and decided to look this post back up. If anyone else ever has this issue, this worked for me. 

  • Like 1
  • 1 year later...
This topic is now closed to further replies.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!