The errors below started on November 4, 2020. I am  out of business without (some of) these.
QUOTE:
Updating DataSet Indices ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 44 symbols...
Error updating Security Names. Invalid URI: The Uri string is too long.
[0]  ^AEX      Error: Invalid URI: The Uri string is too long.
[1]  ^AORD     Error: Invalid URI: The Uri string is too long.
[2]  ^ATX      Error: Invalid URI: The Uri string is too long.
[3]  ^BFX      Error: Invalid URI: The Uri string is too long.
[4]  ^BVSP     Error: Invalid URI: The Uri string is too long.
[6]  ^GDAXI    Error: Invalid URI: The Uri string is too long.
[3]  ^GSPC     Error: Invalid URI: The Uri string is too long.
[3]  ^IBEX     Error: Invalid URI: The Uri string is too long.
[4]  ^IXIC     Error: Invalid URI: The Uri string is too long.
[7]  ^HSI      Error: Invalid URI: The Uri string is too long.
[3]  ^JKSE     Error: Invalid URI: The Uri string is too long.
[4]  ^KS11     Error: Invalid URI: The Uri string is too long.
[7]  ^MERV     Error: Invalid URI: The Uri string is too long.
[5]  ^DJI      Error: Invalid URI: The Uri string is too long.
[4]  ^MID      Error: Invalid URI: The Uri string is too long.
[0]  ^BSESN    Error: Invalid URI: The Uri string is too long.
[3]  ^NDX      Error: Invalid URI: The Uri string is too long.
[0]  ^NYA      Error: Invalid URI: The Uri string is too long.
[1]  ^FCHI     Error: Invalid URI: The Uri string is too long.
[2]  ^FTSE     Error: Invalid URI: The Uri string is too long.
[5]  ^N225     Error: Invalid URI: The Uri string is too long.
[4]  ^MXX      Error: Invalid URI: The Uri string is too long.
[8]  ^N300     Error: Invalid URI: The Uri string is too long.
[7]  ^MSH      Error: Invalid URI: The Uri string is too long.
[3]  ^NZ50     Error: Invalid URI: The Uri string is too long.
[0]  ^OEX      Error: Invalid URI: The Uri string is too long.
[1]  ^OSX      Error: Invalid URI: The Uri string is too long.
[2]  ^RLV      Error: Invalid URI: The Uri string is too long.
[5]  ^RUA      Error: Invalid URI: The Uri string is too long.
[4]  ^RUI      Error: Invalid URI: The Uri string is too long.
[7]  ^RUT      Error: Invalid URI: The Uri string is too long.
[3]  ^SML      Error: Invalid URI: The Uri string is too long.
[0]  ^SSMI     Error: Invalid URI: The Uri string is too long.
[1]  ^STI      Error: Invalid URI: The Uri string is too long.
[5]  ^TWII     Error: Invalid URI: The Uri string is too long.
[2]  ^STI.N    Error: Invalid URI: The Uri string is too long.
[5]  FTSEMIB.MI Error: Invalid URI: The Uri string is too long.
[8]  000001.SS Error: Invalid URI: The Uri string is too long.
[6]  ^NDXE     Error: Invalid URI: The Uri string is too long.
[9]  ^NSEI     Error: Invalid URI: The Uri string is too long.
[4]  ^VAY      Error: Invalid URI: The Uri string is too long.
[7]  ^VIX      Error: Invalid URI: The Uri string is too long.
[0]  ^VXN      Error: Invalid URI: The Uri string is too long.
[3]  ^XAU      Error: Invalid URI: The Uri string is too long.
Update completed (0.328 sec)
----------------
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        I think it's expired cookie. Yahoo is free to change something on their end, you know. If you let WLD run overnight like I did you may experience this. Restart WLD every day and data update should work.
    
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        Thanks! That worked.
    
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        Kept WLD running for 2 days under Visual Studio's debugger hoping to catch the error but it has disappeared since then. LOL
    
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        Same story today: no error. If I'm right and the cookie expires it may be doing that sometime after 24 hours or even later.
    
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        Today I had the URI error too... for the first time. 
And WL was not running in the background .... just started up.
But restarting WL helped ... thx.
    
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        I got the same error today but nothing fixes it. It used to happen before but rebooting the PC helped every time. After trying different things I uninstalled the antivirus and the VPN software, cleared the cache, and deleted cookies but nothing changed. I am stuck.
    
    
        
    
    
        
    
    
        Size:  
    
        Color:  
    
    
 
    
        
     
    
        
    
 
    
    
    
        Yahoo is just one of the many providers - moreover, it's a free feed that comes without any warranty. You can be certain that they do not want you making automated data downloads though. Here's a list of replacements for WL6:
Wealth-Lab 6 Data ProvidersWL6 is completely unsupported. Yahoo's working in WL8 but even if it failed it would took some time to notice (for U.S. stocks) because WL8 has a built in failover and would simply request the data from next enabled provider. In addition to the WL6 providers (which received a lot of improvements in WL8), the new version has wider coverage (IB, TDA, Alpaca, CSI, Tradier...) - with Norgate data coming soon.
All About WealthLab 8 Intraday and Realtime Data Providers 
    
        
    
    
        
    
    
        Size:  
    
        Color: