Does anyone else have trouble updating iShares Core S&P 500 Index ETF (XUS)
Since late January 2026 when I bought units in iShares Core S&P 500 Index ETF (XUS), Quicken does not update the price (high, low, close and volumn) for it.
Is anyone else having this issue?
Answers
-
Hi @Scouter_Don,
Thanks for reaching out to the Quicken Community.
Let me ask you this question: Does the ticker symbol match the security?
To check, go to Tools > Security List.
I look forward to your reply.
Quicken Carlos
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
Since it's a Canadian Security doesn't it need an exchange identifier (prefix)? So TSE:XUS would be the ticker symbol?
0 -
This issue contines as of today's date (May 6 2026) with no change since my original post (April 9 2026).
Of the 20 tickers that I update using the UPDATE button in Quicken Investments, only XUS is an issue. I did have an issue with three stocks in the past (Spring 2025) including CNQ and VRN but that was resolved for all except for VRN which was delisted from the TSX exchange when it merged with WCP (merged May 12, 2025 and delisted effective May 13, 2025).
In the Canadian version of Quicken the exchange does not need to be used as a prefix. Below is a sample of stocks and ETFs that I try to update. CNQ, MFC and XIU (and 16 others) all update without issue. XUS does not.
The only auto updating I use s from Quicken. In general Canadian brokers )and in my case my Canadian brokers), do not offer auto updating.
I have also included screen shots of CNQ and XUS details so you can see that no prefix is included. Nevertheless, CNQ updates perfectly while XUS does not.
I suspect this is a Quicken problem limited to the one ETF/stock (XUS) and it needs to be referred to Quicken Canada for correction.
0 -
Consider this a shot in the dark:
It appears you have setup several unique security types (Stock Energy and ETF Index US). Should not be a problem but … have you had success with other ETF Index US types? If you change the type for XUS to something else, does that clear the problem? Do you still have a type=Market Index?
1




